ultra-statuslisted

# ultra-status — Phase 3.6 Single-call dashboard. Pulls task state from state.db (authoritative), layers in `.ultra/test-report.json` + `.ultra/delivery-report.json` (file artifacts), reports progress + risks + workflow routing. ## Authority failure boundary `task.list` and `task.get` are the only task-state inputs. If either is unavailable or returns an authority error, surface it and stop. Never fall back to `.ultra/tasks/tasks.json`. On `LEGACY_STATE_MIGRATION_REQUIRED`, instruct the user to run `ultra-tools migrate --from=4.4 --to=4.5 --source-dir <project-root>`. ## Workflow ### Phase 0 — Environment validation | Check | If missing | |-------|-----------| | state.db reachable through `task.list` | suggest `/ultra-init` only when `.ultra/` is absent; otherwise surface the MCP error | | At least one task visible via `task.list` | suggest `/ultra-plan` | | `task.list` returns valid rows | surface error | ### Phase 1 — Load data ```jsonc // MCP: task.list (no filter — get all tasks) {} // → { tasks: [...], count: N } // MCP: session.list (active sessions; Phase 4.5.4) { "status": "running" } // → { sessions: [...], count: N } // MCP: session.subscribe_events (recent events for the "last event" panel) { "since_id": 0, "limit": 20 } // → { events: [...], next_since_id: M } ``` Also read: - `.ultra/test-report.json` — if present - `.ultra/delivery-report.json` — if present Extract: - Task stats: by status (`pending`/`in_progress`/`completed`/`blocked`), by priority