Repository navigation
Align PR automation RFC with merged contracts and rollout status - #181
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
The PR automation RFC still described the superseded combined finding schema and a 60-review default, and its checklist did not distinguish merged changes from rollout acceptance. Update it to the merged Direct 1.1 / Strict 1.3 carried-finding contract, verified CI proof, initial 20-review Shanghai schedule, queue fairness and 14/30-day idle ladder.
The implementation checklist links to merged provider and bot PRs at an explicit checkpoint. Ready notifications, board completion, deployment and observed acceptance remain pending. Exposure increases still require at least three successful nightly runs.
Validation: documentation links, source citations and strict SPEC freshness checks pass. The mandatory code review gate approved iteration 1. Documentation only; no knowledge pages changed.