Review the corrected evaluation-integrity control plane - #7
Merged
Merged
Conversation
Distribution verification runs the previous protected validator against a candidate tree, so the corrected payload and the validator that admits it cannot land together. Land the reviewed validator first, against the unchanged 0.2.1 payload: it pins the exact evaluation eligibility policy and schema digests, requires the eight recorded exclusions, refuses the newly excluded effectful skill payloads, and accepts a candidate skill split that moves entries between packaged and blocked while the skill total and component count stay exact.
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.
Updates only the reviewed control plane, ahead of the corrected
0.3.0payload.Verification runs the previous protected validator against a candidate tree, so a
payload whose invariants changed cannot land in the same pull request that teaches the
validator about them. This lands the validator first, against the unchanged
0.2.1payload, so the corrected payload can follow.
What changes
the skill total and component count stay exact, so the already-published
0.0.1-candidate.1payloads and the corrected0.0.2-candidate.1payloads both verify.Verification
All seven checks pass against this tree under the previous protected validator:
exact-inventory,canonical-byte-parity,native-manifest-parse,checksums,fixture-provenance-record,pack-install-smoke-uninstall,canary-rollback-simulation.The payload is untouched, so nothing about the published
0.2.1distribution changes here.