ultra-testlisted

# NOT for running unit tests (that's `ultra-dev`). This audits whole-system integrity before delivery. This is the one end-of-change sensor allowed by PHILOSOPHY C4: an export cannot be called orphaned while a later task may still wire it. It is a terminal sensor, never a gate; the owner decides what to fix or accept. ## Before you start 1. If model-selected, verify the live execution grant in `../ultra-change/references/execution-grant.md` — a current session-local activation or a stably verified durable work-package grant; without either, stop. 2. Read `../ultra-change/references/change-contract.md` and apply its **Active Change authority resolution** before reading any active `intent.md` or resolving a current `change_id`. This workflow requires its one valid active authority; any zero result or typed diagnostic stops before audit input is read until the stated repair or retry succeeds. Read `.ultra/tasks.json` and only tasks whose `change_id` matches the active Change. Every matching task must be `completed` in that sole task-status authority. Read each task's `context_file` Acceptance, Completion, Task Review and closing `## Resume Note`. Historical tasks are not part of this audit snapshot. For every current Change task, require a current `ultra-task-evidence-v2` record whose context, subject, acceptance, and task-review bindings satisfy `../ultra-plan/references/task-evidence-v2.md`. A legacy context Status or Complexity header and v