feat(release): define qualification evidence contracts - #2961
Open
JerrettDavis wants to merge 5 commits into
Open
feat(release): define qualification evidence contracts#2961JerrettDavis wants to merge 5 commits into
JerrettDavis wants to merge 5 commits into
Conversation
Contributor
PR governanceThis PR does not yet satisfy the required template fields:
Please update the PR body, or move the PR back to draft while it is still in progress. |
JerrettDavis
marked this pull request as ready for review
August 13, 2026 05:19
JerrettDavis
requested review from
DevanshiVyas and
chopratejas
as code owners
August 13, 2026 05:19
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
# Conflicts: # pyproject.toml
…-contracts # Conflicts: # pyproject.toml
JerrettDavis
force-pushed
the
jd/release-evidence-contracts
branch
from
August 22, 2026 03:46
e3eeb86 to
978430a
Compare
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.
Description
Define the canonical, versioned evidence contracts required before Headroom can safely qualify exact
mainSHAs and migrate publication to a protectedreleasebranch.The release migration preflight found that #1490 provides deterministic runtime rollout identity, but X-102 and its required evidence contracts do not exist on
main. This PR implements the earliest prerequisite, X-001A. It deliberately does not createrelease, retarget Release Please, or alter publication behavior.Related planning work: X-001A and H-106.
Type of Change
Changes Made
main/releasesemantics, immutable artifact identity, A1-versus-B benchmarking, the black-box benchmark boundary, and auditable overrides.jsonschemapackage as a direct development dependency.mainand retained upstream's Ruff0.16.3pin.Testing
Latest focused validation
The combined local suite that included
tests/test_rollout.pycould not collect in the isolated conflict-resolution worktree because that worktree did not contain the locally builtheadroom._coreextension. The contract, workflow, and governance suites above ran successfully. GitHub CI is authoritative for the full matrix.Real Behavior Proof
resolve_rollout({}).to_dict()snapshot; mutate schema versions, rollout eligibility, revocation, evidence status, Gate B equivalence, A1/B optimization state, and unknown fields.releasebranch, ruleset, lifecycle variable, promotion flow, benchmark dispatch,release-policycheck, or publication path was created or enabled.Runtime Rollout Safety
release-policycheck.Review Readiness
Checklist
CHANGELOG.md; Release Please owns itScreenshots
Not applicable. This PR defines machine-readable contracts and architecture decisions.
Additional Notes
Current release path
A published GitHub Release can still reach publication jobs. H-106 must remain inactive until X-102 can assemble authoritative qualification evidence and emit the stable
release-policycheck. H-107 must add the final publication guard.Dependency justification
jsonschemais mature, pure Python, and already present inuv.lockthrough existing dependencies. This PR makes it direct without adding or upgrading a resolved package.Next bounded work
Continue with H-101, then the remaining evidence producers and X-102. Do not activate H-106 merely because these schemas have landed.