[codex] optimize intake contracts - #3
Merged
Conversation
bigsmartben
marked this pull request as ready for review
July 1, 2026 05:54
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
1 participant
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
source_refs, and stable blocker-code enums across PRD, test-case, visual, HTML SSOT, and IR artifacts.component-state, remove command-owned blocker drift, and require validator-owned readiness output.Why
The prompt review found several instruction-boundary risks: source manifest contracts disagreed with schemas for remote sources, blocker codes were not machine-enforced, HTML SSOT command prose could drift from validator output, and release artifacts lacked source-backed provenance for the integration fork.
Impact
Downstream Spec Kit intake users get stricter, more deterministic validation without losing explicit remote-source gap reporting. Release consumers also get provenance metadata that ties artifacts back to repository, version, source commit, download URL, and validation evidence.
Validation
requirements-dev.txtinto the bundled Python runtime afterpytestwas missing.python -m pytest -qvia bundled Python: 71 passed.git diff --check: no whitespace errors.