v1.0.11

Base Context 1.0.11

Fixes

• Restored recovery compaction for long-running sessions that use prime_context without a request-budget profile.
• Deferred pre-turn recovery until a real containing request establishes replay coverage, without reporting a false compaction failure.
• Preserved exact recovery coverage across over-budget requests and repeated summaries.
• Kept valid full-native payload-hook metadata compatible with optional replay-contract capture.
• Fixed large-session status, listing, and attachment by reading captured usage totals instead of the entire journal.
• Fixed /tree, /context, fork-message selection, and refinement history reads over large unrelated archives.
• Fixed small selected forks over large histories while preserving required updates, invocation records, ancestry, and copy limits.

Checks

• 220 tests passed across the final focused files. Eight existing runtime fork cases and the existing refinement controls also passed.
• Full source, installer, and browser checks passed on Node 22.12.
• A captured 197 MB session passed real isolated daemon open, detach, same-session reattach, tree/context views, message selection, and small-fork creation.
• Native automatic recovery and a fresh-process resume with another summary retained all three recovery records with no failed compaction outcomes. The following main request shrank from about 7.25 MB to 69 KB. These probes used local fake responses, not paid inference.

Replay acknowledgements, source identity, cancellation, dependencies, and selected-output limits remain enforced. Full-history exports/copies and provider requests remain capacity-bounded. This release does not update or restart any running session, sub-agent, kernel, schedule, or external job.