os-sdlc: required-work-check without an id prints its own usage #839
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#839
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
os-sdlc-required-work-checkwith no argument prints the usage text ofretired-tests-check. The agent then gets a usage line for the wrong command. Both commands go throughBoot::Inputs.implementation_checktoDispatchCommands::ArgsHolder#implementation_id!, and that method names one command only.Reproduce
Approach
The usage error names the command that ran. The command name comes from the Boot command table entry.
Required work: none beyond the acceptance criteria.
Acceptance criteria
os-sdlc-required-work-checkruns, then its usage error namesos-sdlc-required-work-check.os-sdlc-retired-tests-checkruns, then its output is unchanged.Owner sketch
OsSdlc::Parser::DispatchCommands::ArgsHolder#implementation_id!(command): the usage error names the given command: "os-sdlc- requires an implementation id, e.g. os-sdlc- 7".OsSdlc::Controller::Boot::Inputs.implementation_check(command): returns the input lambda for one command; the reroute-request input passes "reroute-request".OsSdlc::Controller::Boot::Commands: wires retired-tests-check, required-work-check and mutation-check each with its own command name.Origin
72fc9ff8)Design
docs/takedown/839-tracer/final-design.json(basecf6bd2ca92ab1cccc98d59cc83c78a8b3f00dae8). Placefailing_testsandcode_filesfrom this file exactly as given.Work started: takedown tracer for #972 on branch
prism-architect(persistent worktree), maptakedown-implement, designdocs/takedown/839-tracer/final-design.json.Resolution
Done: required-work-check, retired-tests-check and mutation-check each name their own command in the missing-id usage error; reroute-request passes its own name. Placed from the hand-written takedown design by the takedown-implement map (tracer for #972).
Evidence: Implementation 35 reached merge-ready (implementation_complete), commit
fe5584e0; suite gate green; tests/controller/boot_implementation_id_usage_test.rb red at base, green after; all four placed files byte-identical to docs/takedown/839-tracer/final-design.json.Follow-ups: none