fix(tools): keep the tool that was running when the interrupt landed

[ericleepi314]

What

Pressing Esc mid-tool erased the tool. The transcript kept the calls that had already finished and the "Interrupted · …" note, but the one row that said what was cut off — the command still running — vanished with the turn.

A tool that never completes never gets a completion event, and activeTools is dropped on interrupt.

before                                          after
❯ PROBE bash {"command": "sleep 30", …}         ❯ PROBE bash {"command": "sleep 30", …}
· Interrupted · What should dsh-ccTUI do…         Ran 1 shell command

                                                (ctrl+o)
                                                ⏺ Bash(sleep 30)
                                                  ⎿  Interrupted · What should dsh-ccTUI do instead?

Claude Code 2.1.235, Esc four seconds into a long find:

⏺ Bash(find / -name '*.zzzznope' 2>/dev/null)
  ⎿  Interrupted · What should Claude do instead?

and its collapsed view folds that row into the brief (Searched for 1 pattern) like any other settled call — which is why the note attaches as an ordinary result and not an error. An error would break the row out of the brief and read as a failure it was not.

Printed once

The note had been the reply text too, so carrying it on the row would print the same sentence twice, three lines apart. The reply now keeps only the model's own partial text. With no partial text at all, the shelf hangs off a bare trail message the way a settled segment does — an assistant bubble with no text rendered as an empty ⏺ row.

Also: a workflow was identified by the script it runs

before   ⏺ Workflow(script: log("hello from the workflow") return { ok: true }, met…)
after    ⏺ Workflow(gap-probe)

A script is payload like a file's content, so it joins the bulk set. And an object argument carrying its own name (a workflow's meta block) now renders as that name — as JSON the identity sits behind a brace and two quotes, and the row's 64 columns lose it to the ellipsis, which is the one thing the parens exist to prevent.

Test

• npm run typecheck, npm test — 150 files / 1942 passing
• node scripts/verify-boundary.mjs
• new: the in-flight tool survives the interrupt with its note, and the note is not also the reply (createGatewayEventHandler.test.ts); a workflow renders as its meta name (toolArgs.test.ts)
• live captures: interrupt probe + scripts/tool-gallery.py workflow

🤖 Generated with Claude Code