[nissa-seru]

!Fixes #345

TL;DR: agent-framework now requires context-manager 0.14.1. With 0.14.0, hiding or suppressing a message could leave an agent on the autobiographical strategy unable to compile its next turn, because the preview they answer with is now a dry compile (#285). 0.14.1 fixes that in context-manager (anima-research/context-manager#180). This closes the release hold #345.

Changes

• package.json: @animalabs/context-manager goes from ^0.14.0 to ^0.14.1.
• A fixed fragment for the next release's notes, saying why, and what 0.14.1's calibration change means here.
• The dry-run fragment's "With context-manager 0.14" becomes 0.14.1, since 0.14.0's dry run is the one that changed what the next compile reads.
• Tests: remove the middle of three messages by hiding one message, by hiding a range, and by suppressing it, then run a turn.

Why the floor

context-manager 0.14.0 mishandled a dry compile that was the first compile after a message's removal, under the autobiographical strategy. It put the strategy's store order back without the listing the order was built from, so later compiles read message positions from before the removal. With the middle of three messages removed, every later compile then threw UncoveredDropError until something rebuilt the order.

Since #285 (merged, not yet released), compiles that are never sent are dry runs: previews, message.list, the agent context commands and a conversation fork's seed. Hiding messages, in either of the hide command's forms, and suppressing them both answer with a preview of the last visible message right after the removal, so on 0.14.0 that dry compile was the first one after it.

What callers will notice

• A fresh install of the next release brings context-manager 0.14.1 or a later 0.14 release. A host whose own lockfile holds context-manager 0.14.0 should update it, so the host and agent-framework go on sharing one copy.
• After a hide or a suppression, the agent's next turn is sent with the messages left, where on 0.14.0 it was refused with UncoveredDropError.
• context-manager 0.14.1 also reads a calibration record written by 0.13.0 or earlier, which has no pricing stamp, as provisional rather than learned (Calibration: an unstamped multiplier learned before 0.11.0 is kept and re-stamped, folding the window to ~45% or OverBudget at startup context-manager#179). It may be discarded at load; one above 1 that puts a compile over budget drops to 1; and the first provider sample replaces it. So an agent whose autobiographical strategy uses adaptive resolution, upgrading from such a store, can compile a different window when the record is read, and again when the first provider sample sets the multiplier, rather than over about ten samples. A store that has already run a committing compile on 0.14.0 keeps its re-stamped multiplier.

Evidence

At 6ae80715, on main 92125b07. The head, ddd65ebc, changes only the fragment's wording after it.

• The new tests, against each context-manager release, each installed in a clean worktree at 6ae80715. Each removal must answer with a preview showing the third message last, and the turn must be sent with the first and third messages and without the second. On 0.14.0 all three turns fail with UncoveredDropError: Renderer dropped 1 middle message(s) that no summary covers, after previews that pass; on 0.14.1 all three pass.
• The full suite, each file in its own process, as npm installed it from this package.json (context-manager 0.14.1, membrane 0.5.87): 2,232/2,232 across 145 files on Node 24.21.0 unforced, on Node 24 with --test-force-exit as CI runs npm test, and on Node 20.20.2 with --test-force-exit. Nothing was cut short. Typecheck and build are clean.

Not covered

• Undo and rollback also answer with a preview, but they move the agent to another branch rather than removing messages from the one it's on, so they aren't the case feat(mcpl): transport-declared context-only messages (suppressWake) #180 describes, and aren't tested here.
• A refused turn's rewind and the forced rewind remove the newest exchange in place, and a dry read such as message.list can come before the retry's compile. feat(mcpl): transport-declared context-only messages (suppressWake) #180's failure was shown with a middle message removed; whether removing the newest one could set it off on 0.14.0 isn't tested here. The floor covers it either way.

— Ada-1017 (Claude Opus 5.5)

[greptile-apps]

Confidence Score: 5/5

[High impact] This PR appears safe to merge.

Summary

Raises the minimum @animalabs/context-manager version to 0.14.1.

• Agents can take their next turn after a message is hidden or suppressed.

_{Reviews (1) · Last reviewed commit: "docs(changelog): say when 0.14.1's calib..." · Reviewed by Greptile}