v0.9.0 Workflow: product-readiness tracker

[Hmbown]

Problem

The v0.8.67 candidate includes workflow runtime/library foundations, but Workflow is not product-ready: there is no stable model-facing tool, no normal TUI/CLI run path, no compact run view, and no finished high-fan-out resource story.

This issue is the v0.8.68 umbrella that keeps the release from treating scattered runtime work as a shipped product.

Product-ready definition

Workflow is product-ready when a user can ask CodeWhale to run a workflow, watch it progress in a compact phase-first background-tasks view, inspect/replay artifacts, and recover from failures without crashing the TUI, flooding the parent transcript, or hand-managing worktrees.

Required issues

• v0.9.2 Workflow: wire the model-facing workflow tool and run driver #2974 — model-facing workflow tool, JS/runtime driver, and TUI/CLI run path
• v0.9.1 Workflow: rename user-facing WhaleFlow surfaces to Workflow #4037 — rename user-facing WhaleFlow surfaces to Workflow
• v0.9.2 Workflow: background task phase ledger UI #4039 — background task phase-ledger UI inspired by Claude Workflow's Analyze / Verify / Synthesize panel
• v0.9.4 WhaleFlow: Conductor agent type for orchestrating agent ensembles #4010 — orchestrator/conductor agent for workflow execution
• v0.9.4 WhaleFlow: agent checkpoint and resume on timeout/interrupt #4011 — checkpoint/resume on timeout or interrupt
• v0.9.4 WhaleFlow: agent topology primitives (fan-out, pipeline, diamond, speculative) #4012 — topology primitives: fan-out, pipeline, diamond, speculative, critique loop
• v0.9.4 WhaleFlow: verification gates (compile, test, lint, review as post-agent hooks) #4013 — verification gates after worker completion
• v0.9.0 Performance: TUI lag and memory pressure from high agent fan-out sessions #4014 — TUI lag and memory pressure under high fan-out
• v0.9.4 WhaleFlow: context budget management for high-fan-out orchestration #4015 — context budget management and compact result storage
• v0.9.4 WhaleFlow: worktree pool management for parallel agent isolation #4016 — worktree pool management and cleanup

Acceptance

• A model can call workflow(...) and run an example from workflows/*.workflow.js end-to-end.
• The TUI has a visible Workflow background-tasks panel or sidebar state grouped by phase, with pending/running/done/failed node status.
• Worker rows expose compact telemetry: agent/profile, token count, tool count, elapsed time, and status.
• Parent transcript growth is bounded; full outputs are artifact-backed and retrievable.
• High-fan-out runs do not create unbounded memory, render, or worktree pressure.
• Failed/timed-out workers can checkpoint and resume or escalate cleanly.
• Verification gates can block promotion of failed outputs and appear as a first-class Verify phase when present.
• Public docs and UI call the feature Workflow, with WhaleFlow treated as legacy/internal naming.
• Changelog/release notes are explicit about what shipped as foundations versus what remains product work.