Register v0.9 common population and prospective release contract - #273
Merged
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
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.
The next normal release needs one immutable population identity across the existing corpus and Swift. Register the exact 1,108-case union and a non-executable plan for 92 partitions / 4,252 rows, grouped into 84 executions. The current CLI already discovers all 108 Swift cases; the named population pins that complete set rather than changing default discovery.
Add a separate v0.9 release wrapper that requires an actual freeze and exact evidence SHA, preserves the v0.8 checker, and binds per-report membership. Record the dated pin review in a versioned appendix because the original adapter document is hash-bound by R2. CodeQL must align on 2.27.1 across all new partitions; held non-Swift pack compatibility remains unresolved.
No analyzer matrix, freeze, tag or deployment is performed here. Final executable commands, immutable output capture, runtime verification, storage/control budgets and parent review remain required before execution. Historical reports, outcomes, tools and review hashes are unchanged.
Validation: cargo fmt --check; all 285 Rust tests; 6 population/plan regressions; 5 v0.9 release-gate tests; 13 historical v0.8 gate tests; 7 release-harness tests; both prospective plan checks. References #220 and #215; this PR does not close them.