Add review evidence pack and clarify draft milestone decisions - #9
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 435afdfe37
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
pramodbn-cloud
approved these changes
Aug 9, 2026
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.
What changed
This bundles the current spec review follow-up into many small commits.
Normative and milestone updates:
Review infrastructure:
reviews/documentation for evidence tracking, decisions, framework mappings, scenarios, and external review invitesWhy
The repo needed a concrete evidence layer to move milestone claims from prose toward reviewable, test-backed artifacts. The documented decisions also close ambiguity around retries, transport bindings, and unknown-value handling.
Impact
Maintainers and reviewers now have a structured path for milestone close-out, and implementers have clearer examples for both accepted extensions and rejected closed-vocabulary values.
Validation
UV_CACHE_DIR=/tmp/uv-cache uv run pytest