Persist selected target in artifact.yml so stepper briefs resolve multi-target project config #305
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#305
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
Surfaced during the /os-sdlc:implement run for #300: in a multi-target .sdlc/project.yaml, the select-target step consumes OS_SDLC_TARGET but the choice is never persisted in artifact.yml, so brief builders emit 'project-config unresolved' defaults (code_path=lib, test_path=test) instead of the target's paths (plugins/os-sdlc/lib, plugins/os-sdlc/tests). Fix: persist the selected target in the artifact at select-target/intake and resolve project config through it when building dispatch briefs. Blocks any multi-target implement run; #300 is paused on this.
Resolution
Done: Persisted the ADR-0088 selected target on artifact.yml at intake and resolved brief project config through artifact.target; multi-target briefs now emit the target's code_path/test_path instead of 'project-config unresolved' defaults.
Evidence: Commit
a639666on main; TDD'd (9 new tests across artifact_test, cli_intake_test, new brief_project_config_test); full suite 748 runs / 0 failures; rubocop clean on touched files.Follow-ups: Captured as none: mid-run target changes have no CLI verb (deferred — targets are per-run by ADR-0088); stepper docs note about intake as persistence point dropped as trivial.