verify

# verify — exercise it, prove it, root-cause failures Two jobs: prove the change works with fresh evidence, and when it doesn't, find *why* before changing anything. "Should pass", a previous run, or someone's self-report are never enough — you run it now and read what actually happened. Read [CONVENTIONS.md](../../CONVENTIONS.md) for the ledger (§2), memory (§4), the resume sweep (§5), multi-agent rules (§8), platform adapters (§9), closing output (§18 — the evidence is the result; don't pad it with suggestions), and data-driven decisions (§19). Load the **discipline pack** for the detected stack from `references/disciplines/` — its "In VERIFY" section tells you how to exercise *this* surface for real (real endpoints and error/auth paths for backend, offline and permission-denied paths for mobile, loading/error/empty states for frontend, a fresh eval-set run for AI/ML). Load any **concern pack** the change touches the same way — e.g. `database.md`'s VERIFY section (run migrations up *and* down, realistic data volume). ## Part A — Prove it works (the evidence gate) Walk **§5.1's evidence gate** for every claim you are about to make — identify the proving command, run it now in full, read the real output, compare it to the claim, and only then speak. This skill is where that gate is exercised hardest: everything downstream treats your verdict as fact. ``` 1. Identify the proving command(s): the full test suite, plus how to exercise the actual behavior (run the endpoint...