live-verifylisted

# live-verify The gate proves the code compiles; only driving the change proves it works. Every nontrivial change gets observed doing its job in a production-shaped run before it's committed. If the project has its own verify/run skill (many harnesses ship a built-in that bootstraps one per project), defer to it for the mechanics and use this skill as the checklist. Adapter: `.claude/ai-dev-kit.config.json` (`gate`, `verify`; legacy `prodVerify` honored as the fallback); a missing field → derive it from the repo and say so. ## 1. Run the full gate Run the adapter's `gate` commands in order (lint · type-check · build, or the project's equivalents). A green gate ≠ verified — it's the entry ticket. ## 2. Run the real artifact Produce a fresh production-shaped artifact (`verify.build`) and run it (`verify.run`), confirming readiness per `verify.ready.kind` (http · tcp-port · exit-code · log-line · file-exists · manual). Never repurpose or disturb a standing dev process — dev modes mask production-only failures. **Domain mechanics live in references/ — read exactly one**, keyed on the adapter's `projectType`; absent, infer the type from the repo (manifests, engine project files), state the inference, and use the closest fit: - web-app / api-service → [references/web.md](references/web.md) - game → [references/game.md](references/game.md) - cli → [references/cli.md](references/cli.md) - library → [references/library.md](references/library.md) - data → [references/data.md](r