fix(context): recover SDK compaction failures through archive-linked fresh sessions #495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/native-compaction-handover"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Close the missing bridge between automatic SDK compaction failures and the host archive-linked handover. No byte/token gate, extra summary retry, working-turn replay or invented authority.
Validation
Six new tests pass: native receipts persist across reopen; intentional cancellation is not failure; archive linkage, exact original evidence, no summary retries, no effect replay; actual assessed remaining work reaches fresh context; policy boundaries retained. Existing 54 focused tests passed. Full suite before rebase: 2619 pass, 1 existing optional skip, 0 failures. Rebased exact-head full suite is running. Typecheck/build pass. Independent review PASS.
Minerva's hook change is a separate shared GitOps PR: it emits this receipt only for real incomplete automatic summaries, never for manual/backoff/operator cancellation. Activation and live behavioral verification remain separate.
Post-merge installation/behavior evidence (not business completion):
6006278b6e, digest sha256:8c6a9929f35f7410cbda4dc8892e42a4d1b7da392b93f60cd66b560f9d41eb5a is verified in the running Minerva container; compiled native receipt and host recovery paths are present. Promotion used the normal owner/GitOps path; application reports Synced/Healthy.No production ledger edits, forced pod deletion, model switch, blanket unpause or replay of uncertain effects was used. Historical retained inputs and the separate assessment-blocked business execution remain to reconcile.