conformance: gated means a CI context is required — the claim alone is not a gate - #392
Open
bdelanghe wants to merge 1 commit into
Open
conformance: gated means a CI context is required — the claim alone is not a gate#392bdelanghe wants to merge 1 commit into
bdelanghe wants to merge 1 commit into
Conversation
…s not a gate First measured run after #390 (snapshot run 34264517316): gate_ready 37 as expected, but gated 90 of 90 and gate-absent 0 — because required-baseline requires pr-claim / pr-claim on every default branch, so "any required context" is true everywhere by construction and says nothing about CI. The claim is the passkey's rung, the human touch #913 keeps outside the CI gate on purpose. gated now excludes pr-claim / pr-claim. A caller whose only required context is the claim is gate-absent (its CI decides nothing — the fail-open set); arming-lane-absent narrows to repos with a CI gate and no armer. The claim is still listed in required_checks; gate_ready is unchanged. Closes #391 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CAE3i1NCfwwSVYScKWvEdd
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.
Closes #391 — a correction the first measured run after #390 forced.
Snapshot run 34264517316:
gate_ready37 as expected, butgated90 of 90 andgate-absent0.required-baselinerequirespr-claim / pr-claimon every default branch, so "any required context" was true everywhere by construction and said nothing about CI. The claim is the passkey's rung — the human touch.github-private#913 keeps outside the CI gate on purpose.gatednow excludespr-claim / pr-claim(inclassifyRepoand insummarize).gate-absent: its CI decides nothing, the fail-open set. Expected ≈ 13 callers outside the 37 without their own gate.arming-lane-absentnarrows to repos with a CI gate and no armer: the six with their owngate/schemaaggregator. True findings — their green waits for a person.required_checksstill lists every context, the claim included;gate_readyunchanged.Tests: the claim-only rules fixture is
gate-absentfor a caller and onlycaller-absentfor a bare repo; totals recomputed with a claim-only row. 31 pass; reader suite 334 pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01CAE3i1NCfwwSVYScKWvEdd
Generated by Claude Code