Thread target into TeaTracker#resolve_slug (multi-target intake broken) [capture] #413

Open
opened 2026-08-16 12:02:05 +00:00 by jared · 2 comments
Owner

Context

Surfaced running /os-sdlc:implement #412. TeaTracker#resolve_slug (plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb:133-139) calls Project.load(@root) with no target. On a multi-target .sdlc/project.yaml this raises TargetSelectionError, which the rescue swallows to nil, and fetch_body then fails with the misleading "no tracker configured". Intake ticket-body fetch is therefore broken for every multi-target project. Adjacent to #410 (GateEvaluator target_name env threading) — same family of dropped-target bugs, different site.
Reproduced 2026-08-16: os-sdlc-runner intake 412 --target os-sdlc failed despite a valid .cc-os/config; a wrapper injecting the slug explicitly worked.
VERDICT: CREATE — reproduced concrete failure with a specific fix site, not speculative.

## Context Surfaced running /os-sdlc:implement #412. TeaTracker#resolve_slug (plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb:133-139) calls Project.load(@root) with no target. On a multi-target .sdlc/project.yaml this raises TargetSelectionError, which the rescue swallows to nil, and fetch_body then fails with the misleading "no tracker configured". Intake ticket-body fetch is therefore broken for every multi-target project. Adjacent to #410 (GateEvaluator target_name env threading) — same family of dropped-target bugs, different site. Reproduced 2026-08-16: os-sdlc-runner intake 412 --target os-sdlc failed despite a valid .cc-os/config; a wrapper injecting the slug explicitly worked. VERDICT: CREATE — reproduced concrete failure with a specific fix site, not speculative.
Author
Owner

Root ticket filed: #418. This ticket is a symptom.

Root ticket filed: #418. This ticket is a symptom.
Author
Owner

Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.

Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#413
No description provided.