feat(tools): run a clock on a tool that is still going

[ericleepi314]

What

A running tool's row said Running… and nothing else, for as long as it took.

before                                                  after
⏺ Bash(for i in 1 2 3 4 5 6 7 8; …)                    ⏺ Bash(for i in 1 2 3 4 5 6 7 8; …)
  ⎿  Running…                                            ⎿  Running… (8s)

Claude Code 2.1.235 runs a live clock on it — a shell call reads $ <cmd> (6s · 7 lines) while it works, so a reader can tell a slow command from a hung one without interrupting to find out.

What can't be matched, and why

The line count needs output while the tool is still running, and deepseek-harness publishes nothing at all between tool/call and tool/result. Traced every event on the bus during a command that prints for eight seconds:

session/event tool/call
session/event session/title
session/event tool/result

So the elapsed half is what can be told truthfully, and that is what the row carries. No progress channel is faked.

Details

Held back for the first second, so a call that returns immediately never flashes a (0s). It rides the 500 ms ticker that already drives the blinking bullet — no new timer.

Test

• npm run typecheck, npm test — 150 files / 1950 passing
• node scripts/verify-boundary.mjs
• two new render cases in toolBrief.test.ts: the clock shows at 6s, and never renders (0s)
• new bash_stream gallery scenario — a command that emits over time is the only way to see a running row at all

🤖 Generated with Claude Code