Probe must-fire cases of a changed cop against main in the pipeline gates #1454
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1454
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The pipeline gates do not test the must-fire cases of a changed or new suppression rule in a cop. A cop change can pass every gate while it misses offenses that main reports.
Observed
Seen on 2026-10-27 and 2026-10-28:
def self.methods.Reproduce
n/a: process defect; see the three tickets above.
Approach
Direction: a cop-change ticket lists its must-fire cases. A gate or the behavior-verifier runs the changed cop and main's cop on those cases and reports any case where main fires and the branch does not. A must-fire case that main already fires on is flagged as not red.
Required work:
must-fireinplugins/os-sdlc/libAcceptance criteria
Origin
VERDICT: CREATE