change-interpreter cannot read tickets from worktree subagents (no tracker configured) #498

Closed
opened 2026-08-24 12:54:44 +00:00 by jared · 1 comment
Owner

Context

2026-08-24 #491 run, implementation 2: change-interpreter settled verdict:error reporting 'no tracker configured', despite a valid .cc-os symlink in the worktree; the main session read the ticket fine. Cost: one wasted implementation-open. Workaround that worked: inline the ticket body in the dispatch brief.

Task

Either have the runner inline the ticket body into the change-interpreter brief at implementation-open, or diagnose why ConfigLocator/tea fails in the subagent environment. Evidence: .sdlc/pipeline.db implementation 2, handoff 1.

Origin

  • Trigger: #491 supervised run 2026-08-24.
  • Chain: wasted implementation <- interpreter cannot fetch ticket <- tracker resolution fails in subagent env.
  • Skeptic verdict: CREATE (verified infra failure, root cause named).
## Context 2026-08-24 #491 run, implementation 2: change-interpreter settled verdict:error reporting 'no tracker configured', despite a valid .cc-os symlink in the worktree; the main session read the ticket fine. Cost: one wasted implementation-open. Workaround that worked: inline the ticket body in the dispatch brief. ## Task Either have the runner inline the ticket body into the change-interpreter brief at implementation-open, or diagnose why ConfigLocator/tea fails in the subagent environment. Evidence: .sdlc/pipeline.db implementation 2, handoff 1. ## Origin - Trigger: #491 supervised run 2026-08-24. - Chain: wasted implementation <- interpreter cannot fetch ticket <- tracker resolution fails in subagent env. - Skeptic verdict: CREATE (verified infra failure, root cause named).
Author
Owner

Resolution

Done: Root cause found and fixed via #500 (merged a0b969c, ADR-0146). The diagnosis in this ticket was misdirected: tracker resolution never failed in the subagent env — it never ran anywhere. RoundCommands.subagent_start (round_commands.rb:22) passed no tracker, so StartSubagent unconditionally defaulted to NullTracker; TeaTracker.for had zero production call sites. The failure was identical from the main checkout. #500 implemented this ticket's first proposed option: body fetched once at implementation-open (orchestrator cwd), persisted in implementations.ticket_body, read into the brief by BriefFacts; NullTracker#fetch_body now raises TrackerUnavailable instead of emitting the placeholder.

Evidence: plugins/os-sdlc/tests/runner/cli_subagent_start_test.rb test_entry_agents_brief_carries_the_ticket_body_with_a_null_handoff (green); open_implementation_ticket_body_test.rb; commit b25598e on main. Live end-to-end confirmation will come free with the planned #492 replay — if its change-interpreter receives a real brief from a worktree, this is proven in production.

Follow-ups: none — the #492 replay doubles as live verification; if it reproduces a placeholder brief, reopen this.

## Resolution **Done:** Root cause found and fixed via #500 (merged a0b969c, ADR-0146). The diagnosis in this ticket was misdirected: tracker resolution never failed *in the subagent env* — it never ran anywhere. RoundCommands.subagent_start (round_commands.rb:22) passed no tracker, so StartSubagent unconditionally defaulted to NullTracker; TeaTracker.for had zero production call sites. The failure was identical from the main checkout. #500 implemented this ticket's first proposed option: body fetched once at implementation-open (orchestrator cwd), persisted in implementations.ticket_body, read into the brief by BriefFacts; NullTracker#fetch_body now raises TrackerUnavailable instead of emitting the placeholder. **Evidence:** plugins/os-sdlc/tests/runner/cli_subagent_start_test.rb test_entry_agents_brief_carries_the_ticket_body_with_a_null_handoff (green); open_implementation_ticket_body_test.rb; commit b25598e on main. Live end-to-end confirmation will come free with the planned #492 replay — if its change-interpreter receives a real brief from a worktree, this is proven in production. **Follow-ups:** none — the #492 replay doubles as live verification; if it reproduces a placeholder brief, reopen this.
jared closed this issue 2026-08-24 20:32:17 +00:00
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#498
No description provided.