docs: make agent context retrieval-oriented (#70) - #71
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
Replace sparkstack's oversized procedural agent context with a retrieval-first router and explicit ownership map.
Changes
Verification
The one non-live failure is environmental: the local sibling checkout provides sparkrun 0.2.32 while this repository's committed lock expects 0.2.36, changing the builder's effective context calculation (3481 vs 4096). The same mismatch makes the uv-lock hook request a lock rewrite. No lockfile change is included; CI should validate against its clean dependency checkout.
No live E2E was run because this is documentation/source-contract-only work and the repository requires a deliberately prepared stack and sibling branch prerequisites before E2E.
Operational impact
No stack update, model rotation, service mutation, registry change, or deployment.
Closes #70
Provenance
Codex thread: 01a0faae-74de-7110-a2b8-d326048e984a