Make red_assert a project-configured, ticket-independent gate so the coding map can gain a test-writer node #451
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#451
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?
Origin: #438 slice 6 seam-design pass, decision D33 / OQ3-A (approved 2026-08-20).
The slice-6 coding map v1 ships as programmer → reviewer with no test-writer node, because the only red_assert command today is
Project#red_assert_command, which is coupled to a per-ticket artifact path. A shared map must not encode a per-ticket path.Task: make
red_assertresolvable from project configuration (.sdlc/project.yaml) like the test and lint gates inGateCommands, independent of any ticket artifact. Then add a test-writer node toplugins/os-sdlc/maps/coding.yamlgated by it.Reference: docs/os-sdlc-rebuild/interface-sketches.md slice-6 section (D33, OQ3).
Resolution
Done: Verified red/green test assertions are project-configured and ticket-independent; poodr-implementation map (with its test-writer node) is now the implement skill's default map.
Evidence: GateCommands#to_h resolves test_command from .sdlc/project.yaml per target (plugins/os-sdlc/lib/os_sdlc/runner/gate_commands.rb:20-22), no ticket-supplied test path in the chain; red-for-the-right-reason judged by test-reviewer node (maps/poodr-implementation.yaml:88-91) per ADR-0052; default map switched in commit
5b2abcf.Follow-ups: none — one observation surfaced to the user in-session for their decision: red_assert_command in .sdlc/project.yaml is dead config (referenced only in project.rb's struct), wire it in or remove it