feat(scan): balance action coverage within finite budgets - #1
Merged
Merged
Conversation
datzle123
marked this pull request as ready for review
July 26, 2026 09:09
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.
What changed
coverage-balanced-v1action scheduling for finite scan budgetsscan.jsonand the HTML reportEvidence
pnpm check: 140 passed, 2 expected service-dependent skipspnpm audit --audit-level high: no known vulnerabilitiespnpm smoke: passed, including a real three-route/three-action budget controlpnpm pack: passedRelease status
This is intentionally a draft release candidate. The behavior fingerprint changed from released
68d4a8cb…to candidatef3f65840…; existing real-project evidence remains correctly bound to v1.3.3 and must be rerun before Phase I can be merged/released with hosted 15/15 qualification.