Remove the OS_SDLC_TARGET env fallback from os-sdlc #577
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#577
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
The user wants no env-var requirements in os-sdlc. The target is always passed as
--target NAMEon the command line. ADR-0182 deleted the write guard and with it the env read that #571 added. The ADR-0088 env fallback still exists in the CLI layer, and the error text names the env var. That text is how agents keep re-adding the env read.Observed
Remaining occurrences after ADR-0182:
Reproduce
n/a: design cleanup, no failing behavior.
Expected
Every read of
OS_SDLC_TARGETis deleted. TheTargetSelectionErrortext names only--target NAME. The two skills stop mentioning the env var. The tests that set or clear the env var are removed. An ADR supersedes the env-fallback clause of ADR-0088.Tasks
--target NAMEOrigin
OS_SDLC_TARGETafter the #575 guard deletion, 2026-09-14