workflow: the Hand a task confirm button says only Assign — name the picked lane and its Project #2254

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: 860a1014446b40ccb2e6300985f9d78e
Branch: dev/4-p463-assign-names-target
Base: 575fadf
At: 2026-11-03T02:27:23Z

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

Written-by: FlyBot Lead

The Hand a task dialog now names each lane's Project in its pick list (#2242) and names the picked lane's Project on the target row (#2241), but the last step — the confirm button — still says only Assign. With two lanes that share a name, the row that identifies them is off-screen exactly when the person presses the button.

Reproduction

1. Two Workflows whose lanes share one name in different Projects (e.g. Writing in Alpha and Writing in Beta), plus one board card.
2. Right-click the card → Hand a task.
3. Pick the second lane (Writing in Beta). The target row says which Project it is.
4. Scroll to the bottom: the confirm button reads Assign — the same word for either lane.

Expected

The confirm button names its target, so the last thing read before the click is unambiguous:

• Workflow target: Assign to <lane> · <Project>
• Bot target: Assign to <Bot>
• No target at all: keep today's Assign, still disabled (that is workflow: with no workflow defined the Hand a task Assign button is enabled and posts an empty workflow id #2245's behaviour, and it must not regress).

Scope

Only the button label. showAssignTo state, canAssign, the posted body {workflowId, taskId, title} (or {botId, taskId, title}), the target list, and the #2244 expansion are untouched.

• File: plugins/workflow/client.js (the confirm button), its test file, one docs line, one changelog.d fragment.
• No generated bundle: plugins ship unbundled.

Verification

plugins/workflow/test/client.test.js on the current main: the red-first assertions fail today (button reads Assign for a lane named Alpha/Beta and for a Bot), and pass with the change; the posted body is asserted byte for byte before and after. npm run verify at the tip, exit 0.

Dedupe

Checked against live main and open/closed issues before opening: #2241 covers the target row, #2242 covers the pick list, #2245/#2252 cover the disabled/empty-target case — none of them covers the confirm button's label. grep for Assign to on live main returns nothing.