feat(context): durable local working memory - #47
Merged
Conversation
Enable durable local context for product writer, fixer, and reviewer loops. Preserve exact observations and published views, validate source-backed updates, isolate reviewer evidence, and recover trace-to-memory gaps without redispatching effects. Add bounded context tools, strict offline configuration, read-only inspection, and an optional native sandboxed local compactor. Retain explicit legacy mode and leave the frozen S9 worktree unchanged. Verification: 541 affected-crate tests, strict Clippy, workspace all-target check, Windows cross-check, rustdoc/doc tests, xtask policy and format gates, and pinned Verus checks passed. Native Linux private-filesystem and compactor projection fixtures passed. Task-quality evaluation remains a separate campaign.
Represent the fixed native runtime library allowlist as static path slices. This preserves the exact filesystem contract and satisfies Windows strict Clippy without suppressing the lint.
Separate runner unit targets, recovery integrations, and product integrations on every native Rust matrix in Foundation and Gate A. Retain the ten-minute ceiling and single-threaded fixtures. Validate Cargo integration target inventory and reject missing, duplicated, or misrouted workflow partitions.
Pin the long-lived role-loop future inside its existing timeout so shared callers do not embed its full state. Preserve cancellation and deadline ownership, and assert an 8 KiB caller-facing future budget. Resolves the Windows large_futures findings in both external benchmark adapters.
dollspace-gay
marked this pull request as ready for review
September 6, 2026 03:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the local-working-memory design end to end for product writer/fixer/reviewer loops, enabled by default, with explicit legacy mode.
Design and operational guide: .design/local-working-memory.md and docs/local-working-memory.md.
Local verification
CI follow-up
Final hosted verification
All 439 checks passed on head
9dde7880f358c691a30b4629cc2a90fd983a536d, including the main-branch merge. All four workflows completed successfully:No failed, cancelled, queued, or running checks remained at verification. The head was zero commits behind main. Strict lint rules and existing job timeout limits remain intact.
Boundaries
This is a draft for review. Cross-platform hosted runner results are tracked on this PR. Native tests can report unsupported host prerequisites; a cross-build is not native runtime evidence.
Inspection reports the exact last published view and explicitly flags an uncovered tail. Trace and checkpoint stores are ordered, not one cross-store transaction. Torn trace tails fail closed for operator repair. Optional inference requires installed executable/weights/native resources; no downloads, raw fallback, or cloud fallback are added.
No real-model quality/cost improvement is claimed. Paired evaluation requires a separately declared candidate/campaign. The frozen S9 worktree and campaign were not changed.
Crosslink result recording was unavailable because its pre-existing session database/readiness daemon failed to open/start; no unrelated tracking repair was performed.