ultra-devlisted

# ultra-dev — Phase 3.4 Drive one task from `pending → completed` using a strict TDD loop, gated by `/ultra-review`. **state.db is the authority**: status transitions go through MCP `task.update`; the projector regenerates `tasks.json` and context-md frontmatter. The skill only writes context-md **bodies** (Change Log, Completion, Dual-Write notes). ## Authority failure boundary All task selection and transitions require the live MCP state tools. If they are unavailable or return an authority error, stop. For `LEGACY_STATE_MIGRATION_REQUIRED`, instruct: ```bash ultra-tools migrate --from=4.4 --to=4.5 --source-dir <project-root> ``` Never fall back to `.ultra/tasks/tasks.json`, direct SQLite writes, or a task CLI. The JSON file is only a projector-owned view. ## Design decisions vs pre-Phase-3 - **Single-write status**: Step 1.5 / Step 5 stop touching `contexts/task-{id}.md` frontmatter or the "`> **Status**: xxx`" line. Only MCP `task.update` fires; projector rewrites frontmatter; humans read body for history. - **Native review path**: `/ultra-review all` delegates bounded review work to the current Host's installed review agents. Review is not an MCP service. - **No `/compact` dependency**: Step 4.4 writes `.ultra/workflow-state.json`; trusted lifecycle hooks preserve and restore it around compaction when the Host exposes those events. ## Prerequisites - `task.list` succeeds against state.db and returns at least one `pending` task ## Arguments - `$1`: ta