feat(release): qualify narrow patches from preserved baseline evidence - #77
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
2 participants
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 release gate currently demands new model runs and an exact-artifact canary for every new package, including narrowly scoped instruction clarifications. Add an explicit baseline-qualified patch path while preserving the full qualification default.
Eligible candidates must stay within a fully qualified baseline's major/minor, preserve runtime source, dependencies and build settings, and bind the candidate tarball/manifest hashes. The sole guide exception is an explicitly reviewed flow-run clarification bound to its exact content. Unknown paths and other guide changes require full qualification. Baseline tags, ancestry, full evidence, seals, and existing freshness limits are rechecked at initialization and publication resume. No boolean bypass is added.
Prepare 8.3.1 using the existing 8.3.0 campaign. Release notes explicitly state that the candidate had no live model eval or canary and that the 76/76 results belong to 8.3.0 only. The original evidence and seals are untouched; the new baseline seal independently regrades the same retained evidence under current verifier authority. Most added evidence files repeat existing content-addressed objects; they are not new provider runs.
A new offline CI job builds and verifies newly declared patch artifacts on Linux before merge. Ordinary development changes without a new release declaration skip this check. Existing release retry/convergence protections remain in use.
Validation: focused eligibility and publication tests passed; 13/13 gated replays reproduced; package smoke, provider-free OpenCode 1.18.6 smoke (21 tests), and actionlint passed. Actual 8.3.1 initialization and evidence verification passed using the tracked patch record and baseline. No paid eval, paid canary, tag, npm publish, or GitHub release mutation occurred.
Baseline freshness remains 72 hours for the original canary and seven days for the matrix; publication must recheck these limits. This PR needs review before merging and tagging v8.3.1.
Final clean-worktree push preflight passed: 1,181 tests passed, one opt-in live smoke skipped, plus package smoke. Typecheck, lint, metadata and build passed.