Check each new test method for red at base in final-red #995
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#995
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 takedown
final-redstep checks each test file, not each test method. A new test that passes at base still counts as red when a sibling test in the same file fails.Observed
In the #977 live run on #194 (
docs/takedown/194-20261010-112121/),final-redpassed with only 1 of 4 new tests red at base (LintDirectoryScopeTest F...).The other 3 tests were vacuous at base.
The grader gave
class_removedand did not notice.Reproduce
n/a: the evidence is in
docs/takedown/194-20261010-112121/.Origin
VERDICT: CREATE
Ticket-skeptic verdict (real run; the VERDICT line in the body was written by the filing agent, not the skeptic): CREATE. Observed in docs/takedown/194-20261010-112121; fix seam RedCheck.run in failing_test_step.rb.
Session: 3f094e92-202f-41fc-8d9c-b591750d9bc1
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-prism-architect/3f094e92-202f-41fc-8d9c-b591750d9bc1.jsonl
jared referenced this issue2026-10-12 13:18:45 +00:00
Resolution
Done: final-red now runs each new test method alone (-n Class#method) and requires every one red at base; a failing-test file with no new method fails closed. One red classifier kept (ADR-0283 d4).
Evidence: commit
7907c2b6on prism-architect; takedown suite 505 runs 0 failures (526 after12d2f052); os-sdlc 1540 runs 0 failures; #194-shape replay test gives red?=false and names the 3 non-red methodsFollow-ups: none: test-DSL/it-block support and diff-test place-tests per-file weakness noted in session report, not filed
Dropped follow-up (ticket-skeptic): TestMethods ignores spec-style test/it blocks, but no such test exists under plugins/, so the need is speculative. Revisit if one appears.