verify

# Verify — evidence before "done" "Verified" is not a feeling; it's output you can point at. Never claim passing without showing it (R5 + verification-before-completion). ## When this fires "verify" / "is this done / shippable / ready to merge?" / just before a commit or PR. ## Runtime neutrality The verification runner and evidence standard are client-neutral. Never infer the active agent from this skill's install path: portable canonical content may be copied into a required client adapter such as `.claude/skills`. Use canonical `AGENTS.md` when an instruction is relevant. ## Fast path — if the Agentsmith CLI is available 1. Run `agentsmith verify` (or the installed-project shim `.agentsmith/agentsmith verify` on macOS/Linux and `.agentsmith\\agentsmith.cmd verify` on Windows). It runs every phase in `.harness/verify.conf` and stops at the first failure). `--list` shows the phases; `--only <tag>` iterates just one. Add `--record <directory>` when deterministic command evidence needs a durable local receipt. The destination must be new; relative paths resolve from the project target. Record mode redacts secret-shaped console and sidecar output before either is emitted. 2. On a failure: read the label + command it printed, explain in plain language what broke, and point at that phase's line in `.harness/verify.conf` to fix or refine. 3. Report the actual pass/fail output — not a summary of intent. The v1 receipt covers deterministic commands only. Ke...