os-sdlc: consume os-backlog Tracker/ConfigLocator instead of runner/tea_tracker.rb

jared commented

2026-08-16 12:47:33 +00:00

Owner

Context

os-sdlc has its own tracker layer at plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb (142 lines). os-backlog already has this layer: plugins/os-backlog/lib/backlog/tracker.rb (128 lines) and plugins/os-backlog/lib/backlog/config_locator.rb (73 lines). The two layers are not the same. Each defect found in one layer is not found in the other.

Tickets #410, #413, #414 and #415 are symptoms of this one root. Each ticket repairs one site in tea_tracker.rb:

#410 — target name not threaded into GateEvaluator.
#413 — target not threaded into TeaTracker#resolve_slug.
#414 — tea --output yaml broken on tea 0.13.0.
#415 — .cc-os/config not found inside a git worktree. os-backlog ConfigLocator already solves this.

A repair of the four symptom tickets does not remove the problem. It moves the problem to the next place where the two layers differ.

Origin

Trigger: audit of tickets #413, #414 and #415, all captured 2026-08-16 from one /os-sdlc:implement #412 run.
Improvised this session: none. The audit made no code change.
Chain: four independent tracker defects in os-sdlc ← os-sdlc reads the tracker through its own code path ← plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb repeats work that plugins/os-backlog/lib/backlog/tracker.rb and config_locator.rb already do. Stop: DESIGN (plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb).
Root candidate: this ticket.

Out of scope

Do not close #410, #413, #414 or #415 as part of this ticket.

## Context os-sdlc has its own tracker layer at `plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb` (142 lines). os-backlog already has this layer: `plugins/os-backlog/lib/backlog/tracker.rb` (128 lines) and `plugins/os-backlog/lib/backlog/config_locator.rb` (73 lines). The two layers are not the same. Each defect found in one layer is not found in the other. Tickets #410, #413, #414 and #415 are symptoms of this one root. Each ticket repairs one site in `tea_tracker.rb`: - #410 — target name not threaded into GateEvaluator. - #413 — target not threaded into `TeaTracker#resolve_slug`. - #414 — `tea --output yaml` broken on tea 0.13.0. - #415 — `.cc-os/config` not found inside a git worktree. os-backlog `ConfigLocator` already solves this. A repair of the four symptom tickets does not remove the problem. It moves the problem to the next place where the two layers differ. ## Origin - Trigger: audit of tickets #413, #414 and #415, all captured 2026-08-16 from one `/os-sdlc:implement #412` run. - Improvised this session: none. The audit made no code change. - Chain: four independent tracker defects in os-sdlc ← os-sdlc reads the tracker through its own code path ← `plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb` repeats work that `plugins/os-backlog/lib/backlog/tracker.rb` and `config_locator.rb` already do. Stop: `DESIGN` (`plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb`). - Root candidate: this ticket. ## Out of scope Do not close #410, #413, #414 or #415 as part of this ticket.

jared added the

plugin/os-sdlc

label

2026-08-16 12:47:33 +00:00

jared referenced this issue

2026-08-16 12:47:36 +00:00

os-sdlc: gate subprocess ignores ticket target_name — false "no target selected" escalations #410

jared referenced this issue

2026-08-16 12:47:36 +00:00

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

jared referenced this issue

2026-08-16 12:47:37 +00:00