Why: Reconcile interrupted dispatch without spending another model request.
Evidence: Core package tests pass locally; integration exercises acceptance and recovery.
Impact: Add one optional persisted run identifier.
Refs: feature/workbench-flow-completion
Why: Retain full results and exact answers across persistence and reload.
Evidence: go test ./... passed locally, including full-tail and legacy JSON coverage.
Impact: Add contract roundtrip tests and a guarded dispatching state.
Refs: feature/workbench-flow-completion
Why: Keep background results and optional decisions outside the foreground conversation lock.
Evidence: Core package tests and combination checks are recorded in the Dev task.
Impact: Add an optional backward-compatible work card payload without a database migration.
Refs: feature/workbench-flow-completion