Fix brief composer's false 'no tracker configured' in subagent-start briefs #494

New issue

Closed

opened 2026-08-23 18:22:29 +00:00 by jared · 1 comment

jared commented

2026-08-23 18:22:29 +00:00

Owner

Context

During /os-sdlc:implement of #490 (2026-08-23), os-sdlc-runner subagent-start composed a dispatch brief with ticket_brief = '(no tracker configured -- ticket body unavailable for 490)' even though .sdlc/project.yaml sets tracker: forgejo:jared/cc-os and os-backlog issue-show 490 returns the full body. The programmer inferred the ticket from the only red test and implemented the wrong change; the reviewer caught it.

Skeptic verdict: CREATE (gauntlet passed, root-vs-symptom: this ticket is the root).

Tasks

Make the runner's brief composer resolve the tracker the way os-backlog's ConfigLocator does (worktree-aware, .cc-os/config / project.yaml)
Fail loudly when tracker resolution fails instead of shipping a brief that invites guessing

Origin

Trigger: /os-sdlc:implement of #490, first programmer round, 2026-08-23.
Improvised this session: none — pre-existing bug in the brief composer, not introduced by #490's work.
Chain: programmer implemented wrong change ← brief said 'no tracker configured -- ticket body unavailable' ← runner's brief composer never resolves the tracker via ConfigLocator even though tracker: forgejo:jared/cc-os is set and os-backlog issue-show works. End: DESIGN (os-sdlc runner brief composition path).
Root candidate: this ticket.

## Context During /os-sdlc:implement of #490 (2026-08-23), `os-sdlc-runner subagent-start` composed a dispatch brief with ticket_brief = '(no tracker configured -- ticket body unavailable for 490)' even though .sdlc/project.yaml sets `tracker: forgejo:jared/cc-os` and `os-backlog issue-show 490` returns the full body. The programmer inferred the ticket from the only red test and implemented the wrong change; the reviewer caught it. Skeptic verdict: CREATE (gauntlet passed, root-vs-symptom: this ticket is the root). ## Tasks - [ ] Make the runner's brief composer resolve the tracker the way os-backlog's ConfigLocator does (worktree-aware, .cc-os/config / project.yaml) - [ ] Fail loudly when tracker resolution fails instead of shipping a brief that invites guessing ## Origin - Trigger: /os-sdlc:implement of #490, first programmer round, 2026-08-23. - Improvised this session: none — pre-existing bug in the brief composer, not introduced by #490's work. - Chain: programmer implemented wrong change ← brief said 'no tracker configured -- ticket body unavailable' ← runner's brief composer never resolves the tracker via ConfigLocator even though tracker: forgejo:jared/cc-os is set and os-backlog issue-show works. End: DESIGN (os-sdlc runner brief composition path). - Root candidate: this ticket.

jared added the

plugin/os-sdlc

label

2026-08-23 18:22:29 +00:00

jared referenced this issue

2026-08-23 18:22:55 +00:00

Gate settlement reply carries step outputs and passed-step feedback #490

jared commented

2026-08-26 17:52:11 +00:00

Author

Owner

Resolution

Done: > This was generated by AI during triage. Closing as implemented — resolved by #500.

Evidence: Commits b25598e/a0b969c (#500) moved ticket-body binding to implementation-open: open_implementation.rb:21 resolves TeaTracker.for(root:) and persists the body on the implementations row; brief_facts.rb:41-42 reads implementation[:ticket_body] first. StartSubagent no longer resolves the tracker at dispatch time, eliminating the false 'no tracker configured' failure mode.

Follow-ups: None.

## Resolution **Done:** > *This was generated by AI during triage.* Closing as implemented — resolved by #500. **Evidence:** Commits b25598e/a0b969c (#500) moved ticket-body binding to implementation-open: open_implementation.rb:21 resolves TeaTracker.for(root:) and persists the body on the implementations row; brief_facts.rb:41-42 reads implementation[:ticket_body] first. StartSubagent no longer resolves the tracker at dispatch time, eliminating the false 'no tracker configured' failure mode. **Follow-ups:** None.

jared closed this issue

2026-08-26 17:52:11 +00:00

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#494

No description provided.

Rows
Columns