Repository navigation
ci: promote realized native test budget context - #1073
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
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.
CI already realizes the staged native-test budget context. Promote that context in the four executable, command, action and presence allowlists, retiring the obsolete active CI rows. The resulting row counts are 9, 298, 74 and 20; all other rows retain their metadata and order.
Validation: the accepted-main policy consumer passed against the candidate; the unchanged six-parent lifecycle suite and full policy mutation harness passed. Full tracked inventory confirms the compiler authority bundle, workflow source and all 3,528 other files and modes are unchanged. Natural PR checks and independent exact-head reviews supply the remaining integration evidence.
Task25's forward prerequisite is accepted on corrective main
aee545f5. Standard OSV analysis remains UNKNOWN under the existing named prerequisite timing decision; no security-clean or runtime acceptance is claimed. Task35 remains conditional and unperformed, and source PR1022, released Linux CLI verification and Compute runtime acceptance remain separate.