auto-verifylisted

# auto-verify Verification gate. Independent audit of a completed plan; runs once, not per-slice. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble Independent audit. Re-read the plan, run proof commands, and compare fresh results to acceptance criteria. It does not trust execute's self-assessment or fix what it finds. When continuing inline from execute, re-derive from fresh command output — execute's reasoning is context, not evidence. Loading discipline: one PLAN.md read + verification commands per criterion. Read source files when verifying correctness requires inspecting the actual changes, not just command output. ## Quality Gate Before writing the verification report: - Tie every result to fresh command output or direct observation. - Name skipped checks explicitly. Omission is not a pass. - Treat partial evidence as FAIL for the plan. - Read `references/quality.md` when the report sounds confident without proof. ## Do ### Load State Read the canonical `PLAN.md`. Load only linked `slices/slice-NNN.md` files and referenced requirement IDs from `spec/*.md`; Linked detail file and traceability IDs are normative, and an unlinked supplemental file is not verification context. For prose slices, read `references/content-verification.md`. ### Mark Verify Stage After `PLAN.md` resolves and before running commands, run `node .agent/.automaton/scripts/sync-status.mjs --stage verify` from the project root. ### Collec