ultra-devlisted

# Take one task from plan to recorded evidence The model owns code reasoning and edits; repository files own the resumable contract. ## 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`. Require its one valid authority; otherwise stop with its typed repair. Then read `.ultra/tasks.json`. Without an exact task id in the owner invocation, select only the uniquely current `in_progress` task and read its full `context_file`, especially `## Resume Note`; if none exists, stop and ask the owner to invoke Dev naming one exact task id — a `pending` row is a frontier candidate, not active work, and Hooks will not have injected its acceptance or Resume. An invocation that names one exact task id supplies invocation-local selection authority for this Dev run only. If more than one row claims `in_progress`, do not manufacture a unique current task; use the explicit recovery below or stop with the Hook diagnostic. The ledger is the sole task-status authority; legacy Status or Complexity never overrides it. A `completed` task with a current invalidation observation may be selected only for the