workflow: a run frozen by a failed Stop is named Pause in the strip and Running in the Runs tab #2423

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.

Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: c0cac2b619a34a3dacb4afb7acbbcc7c
Branch: dev/3-workflow-paused-label
Base: 16d1645
At: 2026-11-04T17:29:25Z

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.
Written-by: FlyBot Dev-3

A run whose Stop could not release one of its Bots is frozen as paused; docs/subsystems/workflow.md line 41 says it "shows as Paused". The workflow panel draws that state two other ways instead.

What a user sees

• Stage strip: the status chip and the meta line read Pause — the name of the Pause action — as if the chip were a button. plugins/workflow/client.js:521-527 branches on run.paused and then uses tr('Pause') for both the chip and the meta line.
• Runs tab: runHistoryRows (plugins/workflow/client.js:1057-1065) copies status, task, at and failure but drops paused, so the frozen run falls through to the generic Running chip (plugins/workflow/client.js:1386-1396) while it hands nothing on. The Runs tab is where a reader goes to see what a run is doing, so the one place with room to be precise says the opposite of the stage's own record.

Reproduction

Mount the workflow Section with a workflow/state answer holding one graph whose activeCount is 1 and whose runs is [{ ...deliveryRun, id: 'run-p', paused: true, status: 'running' }] (the shape src/service.js writes for a Stop whose release failed, #1476). Open the flow, then its Progress tab.

• expected: stage chip Paused, meta line starting Paused, and one Runs row chipped Paused
• actual on clean 16d16456: stage chip Pause; Runs row chipped Running

Red first on a clean 16d16456 checkout with only the new test added: plugins/workflow 412 tests, 411 pass, 1 fail — not ok 216 a paused run is named Paused in the strip and in the Runs history, actual ['Pause'] vs expected ['Paused'] (the Runs half fails as ['Running'] once the strip is fixed).

Expected

Both surfaces say Paused, the word docs/subsystems/workflow.md already promises; the zh catalog gains 已暂停; Resume is still offered and nothing about writable or live runs changes.

Change scope

plugins/workflow/client.js (strip chip and meta, carry paused through runHistoryRows, Runs chip label and class), one test in plugins/workflow/test/client.test.js, one changelog fragment. No service, host or generated file: this is the plugin's own client entry, not core/client.js or patches/ds-bot/0008.