Prose-only tickets have no red path in poodr-ticket-implementation #892
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#892
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
A prose-only ticket has no red path in the
poodr-ticket-implementationmap. Implementation 7 of #874 escalated withunexpected_pass:test-writer/diff-testbecause the seam-designer told test-writer to write no Ruby test. The required-work gate runs only at thesuite-checknode (after programmer), so no node proves a prose ticket is red first. The docs mappoodr-implementationwas removed in #859 slice 1.skills/implement/SKILL.mdstill says docs, config, ADR-only, and spike tickets run on this map. That statement is false in practice.Reproduce
n/a: design gap. Implement any ticket whose increment is prose only; test-writer writes no test and the diff-test gate reports an unexpected pass.
Approach
Choose one option.
required-workas the red gate at test-writer when the ticket has typed checks and no test-shaped increment.Rejected: hand-finishing each prose ticket — it bypasses the pipeline.
Acceptance criteria
Origin
os-sdlcimplementation 7 of #874 escalated (escalation 3,unexpected_pass:test-writer/diff-test).83f95bbc.plugins/os-sdlc/maps/poodr-ticket-implementation.yaml← DESIGN (docs mappoodr-implementationremoved in #859 slice 1).VERDICT: CREATE
Found during #874.
Resolution
Done: Folded into #812 as evidence
Evidence: Same mechanism; see occurrence comment on #812
Follow-ups: none