Skip to content

chore: version packages - #1266

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@martian-engineering/lossless-claw@1.2.1

Patch Changes

  • #1264 150c96f Thanks @jalehman! - Bound the forced overflow-recovery raw tail by tokens when freshTailMaxTokens is unset. Recovery now caps the protected suffix at 25% of its target, so a default 64-message tail full of large tool results no longer blocks recovery with no_compaction_progress. Routine compaction is unchanged.

  • #1284 51c3c90 Thanks @jalehman! - Report compaction progress to OpenClaw and honor its abort signal. Each committed summary pass now refreshes the host's compaction idle timeout, so multi-round overflow recovery no longer fails with "Compaction timed out" while it is still making progress. When the host aborts, the sweep stops before starting another pass and keeps the summaries it already committed.

  • #1263 d4aa0b5 Thanks @jalehman! - Forced overflow recovery now honors the host-observed prompt size when the host owns prompt framing. Lossless scales the host's observed overflow into a stored-token target, so it no longer reports a successful no-op while the host is still over its budget.

  • #1265 f5a9501 Thanks @jalehman! - Stop opening the summary spend backoff when forced overflow recovery makes real progress but cannot reach its target because of the protected tail. Partial recovery no longer blocks foreground compaction on later assembles with deferred compaction backoff active. A forced pass that spends summarizer calls without reducing context still opens the backoff.

  • #1271 aa63cfe Thanks @rabsef-bicrym! - Clarify in the injected recall guidance that lcm_grep requires pattern, not
    query, for both regex and full-text searches. Include a full-text example to
    distinguish it from lcm_expand_query.

  • #1064 8aa975c Thanks @brkastner! - Fix lcm_grep throwing Cannot read properties of undefined (reading 'trim') when a model omits or misnames the pattern argument. Hosts pass
    model-supplied tool arguments through without schema validation, so the
    call died with an uncatchable TypeError before any query ran. The tool now
    returns a tool error naming the expected field, including the query vs
    pattern difference against lcm_expand and lcm_expand_query, so the
    agent can correct the call and retry.

  • #1276 47e8bc5 Thanks @TheAngryPit! - Use the captured registration config for independent log redaction so plugin registration can complete before OpenClaw's global runtime config is prepared.

  • #1270 b00ffb9 Thanks @jalehman! - Keep lossless-claw consistent when OpenClaw reloads the plugin during a running turn. Delegated expansion grants are now stored in the LCM database, so a delegated lcm_expand child no longer fails with "Delegated expansion requires a valid grant" after a reload. Runtime-authored user turns, such as OpenClaw's continuation prompt, keep their internal_system provenance and display: false flag instead of being stored as messages the user typed. On OpenClaw 2026.9.5 or later, disposing the plugin instance also closes its database, so the next plugin generation does not reuse the retired engine.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from aab9e28 to 60d5062 Compare October 27, 2026 16:08
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from bff7310 to 7ae577c Compare November 2, 2026 21:41
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7ae577c to 2270ae5 Compare November 5, 2026 23:12

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants