Record main-loop token usage per implementation #598

New issue

Open

opened 2026-09-15 15:58:58 +00:00 by jared · 0 comments

jared commented

2026-09-15 15:58:58 +00:00

Owner

Context

Split from #590 on 2026-09-15. #590 requested an orchestrator-role dispatch row to record main-loop token usage alongside subagent dispatches. #590 now delivers subagent sweep only. The main loop is not a dispatch.

Observed

implementation-report sums dispatch rows only. Main-loop usage for an implementation is never recorded anywhere in pipeline.db.

Reproduce

n/a: feature ticket. The absence is visible in any implementation-report output, which lists subagent roles only.

Expected

A design decision, then implementation, on two points. Source: the parent session jsonl read at SessionEnd, or the implementation-report reading the parent session jsonl by implementations.session_id. Landing: a synthetic orchestrator dispatch row, or new columns on implementations. Related: ADR-0175 (lazy usage read after agent return).

Origin

Trigger: ticket #590 investigation
Improvised this session: none
Chain: main-loop usage unrecorded ← #590 scope cut ← orchestrator is not a dispatch
Root candidate: this ticket
Where: os-sdlc runner, DispatchCommands.implementation_report (plugins/os-sdlc/lib/os_sdlc/runner/dispatch_commands.rb)
Session: 83e90713-139b-4616-a520-c57dc052c294
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/83e90713-139b-4616-a520-c57dc052c294.jsonl

## Context Split from #590 on 2026-09-15. #590 requested an orchestrator-role dispatch row to record main-loop token usage alongside subagent dispatches. #590 now delivers subagent sweep only. The main loop is not a dispatch. ## Observed `implementation-report` sums dispatch rows only. Main-loop usage for an implementation is never recorded anywhere in pipeline.db. ## Reproduce n/a: feature ticket. The absence is visible in any `implementation-report` output, which lists subagent roles only. ## Expected A design decision, then implementation, on two points. Source: the parent session jsonl read at SessionEnd, or the implementation-report reading the parent session jsonl by implementations.session_id. Landing: a synthetic orchestrator dispatch row, or new columns on implementations. Related: ADR-0175 (lazy usage read after agent return). ## Origin - Trigger: ticket #590 investigation - Improvised this session: none - Chain: main-loop usage unrecorded ← #590 scope cut ← orchestrator is not a dispatch - Root candidate: this ticket - Where: os-sdlc runner, `DispatchCommands.implementation_report` (plugins/os-sdlc/lib/os_sdlc/runner/dispatch_commands.rb) - Session: 83e90713-139b-4616-a520-c57dc052c294 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/83e90713-139b-4616-a520-c57dc052c294.jsonl

jared added the

plugin/os-sdlc

filed-by/agent

labels

2026-09-15 15:58:58 +00:00

jared referenced this issue

2026-09-15 16:35:05 +00:00

dispatches token columns are zero for some implementations (#583, #565, #566, #572-#574) #590