Problem
During the merge phase, the merge agent telemetry (session name, elapsed time, tool count, tokens, cost, last tool) is displayed on every wave in the merge history view, not just the wave currently being merged.
Screenshot
All 5 completed waves show identical merge telemetry (orch-henry-merge-1, 0m 24s, 9 tools, $0.117) even though only wave 6 is actively merging. Waves 1-5 already completed their merges in prior phases.
Expected
- Completed waves should show their own historical merge telemetry (from when they were merged), or no merge telemetry at all if it was not captured
- Only the currently-merging wave should show live merge agent telemetry
Likely Cause
The dashboard reads the current merge agent snapshot from the registry/telemetry and displays it for all waves instead of matching it to the specific wave being merged. The waveIndex field on the merge snapshot (added in TP-164) should be used to associate merge telemetry with the correct wave.
Files
dashboard/public/app.js — merge telemetry rendering per wavedashboard/server.cjs — merge snapshot API response
Problem
During the merge phase, the merge agent telemetry (session name, elapsed time, tool count, tokens, cost, last tool) is displayed on every wave in the merge history view, not just the wave currently being merged.
Screenshot
All 5 completed waves show identical merge telemetry (
orch-henry-merge-1, 0m 24s, 9 tools, $0.117) even though only wave 6 is actively merging. Waves 1-5 already completed their merges in prior phases.Expected
Likely Cause
The dashboard reads the current merge agent snapshot from the registry/telemetry and displays it for all waves instead of matching it to the specific wave being merged. The
waveIndexfield on the merge snapshot (added in TP-164) should be used to associate merge telemetry with the correct wave.Files
dashboard/public/app.js— merge telemetry rendering per wavedashboard/server.cjs— merge snapshot API response