feat(tasks): re-dispatch resumes the prior transcript + jump from a session to its task (v0.320.0)

[vikasprogrammer]

Two related task changes.

1. A task re-dispatch RESUMES the prior transcript (not a fresh restart)

A task is the durable unit of work; a session is one attempt. Every other re-entry path — chat threads, DM replies, poke-back, self-schedule — already --resumes the prior transcript. Task re-dispatch was the lone exception: it spawned a fresh session with only a text summary of the last run's outcome (priorRuns), so a retried or reopened task re-derived everything it had already worked out (files read, decisions, half-done work).

dispatchTask now resumes the same transcript when the task's latest run was the same assignee agent and pinned one (TerminalManager.resumableTaskTranscript), seeded with a "continue, don't restart" prompt.

Bounded — the ladder you land on a failing task:

attempt 1: fresh (first run)
attempt 2: RESUME transcript
attempt 3: RESUME transcript
attempt 4: FRESH escape (2 resumes didn't close it → mint a new transcript)
attempt 5: TASK_MAX_ATTEMPTS → park blocked

• MAX_TASK_RESUMES = 2 — after two resumes that don't close the task, start fresh to escape a wedged/looping transcript. A fresh run mints a new claude_session_id, so the streak resets and the last attempt before parking is a clean slate rather than a third reload of a poisoned context.
• TASK_MAX_ATTEMPTS 3 → 4 so the escape-fresh attempt actually runs before the block. (Flagged: this nudges the global per-task retry budget by one.)
• A changed assignee can't resume another agent's transcript → fresh.
• Side benefit: because a resumed dispatch reuses the transcript id, retries now collapse into one conversation in the chain/cost view (cost = max) instead of N separate ones.

Pinned by scripts/task-resume-test.cjs (wired into test:governance) — 17 assertions covering the full ladder, the same-agent guard, and the escape minting a new transcript.

2. Jump from a session to its attached task

The session view couldn't reach the task it works — the edge only existed the other way (task room → its runs). The session facts row now shows a clickable task chip when the run has a task:/poke:/ask: provenance (Session.taskId, already stamped by listSessions' chainLinks), deep-linking to the board card via the same #/tasks/<id> route the inbox uses.

Verification

• npm run build + cd web && npm run build + full npm run test:governance green (incl. the new task-resume test).

🤖 Generated with Claude Code