Ticket map escalates on a documentation-only case: behavior-verifier fails, test-writer unexpected_pass #593
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#593
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?
Context
Implementation 17 on ticket #587 ran the poodr-ticket-implementation.yaml map.
Case 5 of the ticket's
## Casessection asked for a prose change to SKILL.md.The programmer made that edit in round 1, together with the code change.
Observed
behavior-verifier (dispatch 230, 25 s, 2 tool uses) returned fail. It named outstanding tasks.
The map routed the run to test-writer (dispatch 232).
test-writer wrote
tests/skills/implement_skill_default_map_test.rb. The test asserts on the raw SKILL.md text.Its diff-test gate exited 0 at once.
Rubocop then flagged that test three times with
Sdlc/Structural/RawFileContentAssertion.The orchestrator finished the case by hand. It deleted the prose test, committed, and closed the run.
Reproduce
n/a: pipeline-behavior defect, not a single reproducible command
Expected
A documentation-only case must not sit under
## Cases. Per ADR-0190, that section holds one observable given/when/then per line.The
TicketShapecheck must flag a documentation-only line under## Cases.As an alternative or additional fix, the behavior-verifier charter should gain a rule: an outstanding task whose only evidence is a text-file diff is verified by reading, not by routing to test-writer.
Triage picks between these two candidates.
Origin
## Cases)## Cases## Cases; root candidate itself, no in-session duplicate)