Fix intake fact idempotence and bound preflight - #48
Merged
Conversation
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
Fix repeated spec-intake discovery appending implementation-detail facts on every pass. The durable mission projection now records item-to-fact identities, and mission fact capacity is preflighted for the whole assessment before any record or event is written.
This prevents large intakes with several product-answer passes from reaching the 500-fact bound with duplicated facts, and prevents facts.jsonl from advancing beyond mission.json when a batch exceeds the bound. Claude Code and Codex plugin bundles and checksums are regenerated from the fixed sources.
Verification
Checklist
Security impact: no authority boundary is expanded. The change strengthens bounded mission persistence by refusing over-capacity fact batches before writes.