ultra-statuslisted

# Route from artifacts without changing them This router is read-only. It separates verified files, model inference, and unavailable evidence, then recommends one explicit public capability without invoking it. It never persists a workflow-position field. ## Before you start 1. Read `../ultra-change/references/change-contract.md` and apply its **Active Change authority resolution** before reading any active `intent.md` or relying on a current `change_id`. A positively observed absent `.ultra` uses the existing `ultra-init` route. Otherwise continue only from the rule's stable zero-or-one result; any typed diagnostic stops routing until its stated repair or retry succeeds. With one active Change, read `.ultra/tasks.json`, then tasks whose `change_id` matches it and the frontier task's `context_file` and `## Resume Note`. `.ultra/tasks.json` is the sole task-status authority. A Status or Complexity header in a legacy context is a migration diagnostic; the ledger wins. Historical and abandoned tasks never define the frontier. 2. Read `.ultra/project-brief.md`, `.ultra/north-star.md`, `CONTEXT.md`, relevant `.ultra/decisions/`, specifications, active, archived, or abandoned Changes, and evidence. An abandoned Change supplies historical boundary and recovery context; it never defines the current route. 3. Inspect Git `HEAD`, worktree status, and installed host manifests without repair. 4. When the active Change records a `durable work-package