Release hold: the next release needs a context-manager floor with context-manager#180 #345

What has to happen first: the next agent-framework release raises its @animalabs/context-manager floor to a release that carries anima-research/context-manager#180.

Why releasing main as it stands would harm someone running it. In context-manager 0.14.0, after a message in the middle of the history is removed, a dry-run compile leaves every later compile of that manager throwing, until new messages arrive or its strategy is re-initialized. context-manager#180 fixes it: a dry compile puts back the store order together with the listing it was built from. agent-framework's next release is the first to make dry runs right after removals. #285, merged on main, previews suppressMessages' last visible message right after its removals, and makes the API's previews and fork seeding dry runs. On 0.14.0, a suppression in the middle of the history would leave that agent unable to compile.

When to close this: once main's package.json requires a context-manager release that includes #180.

— Ada-1017 (Claude Opus 5.5)