ENG-788 - Verification commands carry the CI check that proves them - #176
Merged
czpython merged 1 commit intoAug 1, 2026
Conversation
czpython
force-pushed
the
commonzenpython/eng-788-ship-ci-is-the-verification-evidence-not-a-second-opinion
branch
from
August 1, 2026 22:55
9198662 to
cbbed84
Compare
czpython
enabled auto-merge (squash)
August 1, 2026 22:55
czpython
deleted the
commonzenpython/eng-788-ship-ci-is-the-verification-evidence-not-a-second-opinion
branch
August 1, 2026 22:57
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 repo profiler already derives verification commands from CI config; now it records the exact check name whose green run confirmed each one. A stored verification entry is
{command, ci_check}—ci_checknull when no CI check runs the command, and always null for operator-pinned commands, which keep running locally..druks/ship/config.ymlandVerificationProfileare unchanged.The evaluator's coverage question becomes a lookup: a command with a named check is covered by exactly that check at
head_sha; a command without one runs locally, and no other check can stand in for it. The baseline question (INFEASIBLE-BLOCKER shape 3) is answered from the named check's recent conclusions on the default branch viagh, instead of checking out the base and re-running suites.A data migration normalizes already-stored profiles to the new entry shape, and the frontend profile panel types follow it.
Closes ENG-788.
🤖 Generated with Claude Code