delivery-workbenchlisted

# Operating Delivery Workbench This repository uses Delivery Workbench: an evidence-first commit gate over a Markdown roadmap under `pm/roadmap/<project>/` (phases, stories, paired evidence files). Markdown is the source of truth; `.githooks/dw` is the CLI for everything below. Run `.githooks/dw doctor` if anything seems miswired. `.githooks/dw-workbench --root .` serves a localhost web view of the roadmap (browse, health, trace, guarded edit). ## Start with one briefing Start every work session with one briefing read; do not call both transports. - `.githooks/dw status [project] --json` — the versioned readiness, workspace, roadmap, and next-safe-action object. Exit 0 means `ready`; exit 1 means `attention`. Attention is valid JSON: follow its blocking repair action before work. Status reads only; it never executes the action. - MCP-capable agents may call `dw_status` instead. It returns the identical object in `structuredContent`; an `attention` verdict is not a tool error. To act on a command recommendation, preview a fresh lease with `.githooks/dw step [project] --json` (or MCP `dw_step`). Require `applicable: true`, review the exact action/token/`apply_command`, and only after explicit authorization invoke that exact command (or `dw_step_apply` with the same `expect` token). Never reconstruct argv. One apply starts at most one child and stops; re-read status and preview a new lease before any next act. Manual/project-selection states, certification, and comm