Reviewer charter: flag lint-induced tests (split from #199, awaiting incident) #228
Labels
No labels
P0
P1
P2
P3
bug
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
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#228
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?
Item 3 of #199, split out. Proposes the reviewer flag tests that exist only to satisfy lint cops. Deferred: asserted provenance (records/run-18) is unverifiable — the jared/os-sdlc repo is retired and no quoted incident exists. Re-open trigger: a quoted os-sdlc run incident showing a lint-induced test slipping past review.
Closing as wontfix: this is a guardrail without provenance. The ticket itself notes the cited run-18 incident is unverifiable (jared/os-sdlc retired, no quoted incident exists), and the house rule is that charter/guardrail additions need real provenance or they get cut.
Recorded in
.out-of-scope/lint-induced-test-flagging.md, which preserves the re-open trigger: a quoted os-sdlc run incident showing a lint-induced test slipping past review. If that surfaces, delete the file and re-file.