# /kit-verify — verify this project's kit installation against its manifest

Run the installation verifier and report drift between the installed `.claude` machinery and
`.claude/KIT_MANIFEST.json` (written by bootstrap — provenance at birth for installations).

## Steps

1. Run: `powershell -NoProfile -File .claude/tools/Verify-KitInstall.ps1 -Json` (add
   `-KitSource <path>` when the kit source checkout is available locally — this enables the
   STALE/CONFLICT classes). Parse the JSON.
2. Summarize for the human, grouped by class, worst first: **CONFLICT** (locally modified AND kit
   moved — needs a hand-merge decision), **MODIFIED** (freelanced edit — offer the three exits:
   graduate the change into kit source, declare it in `.claude/KIT_OVERRIDES.txt`, or restore via
   re-bootstrap `-Force`), **MISSING**, **STALE** (re-bootstrap), then counts only for OVERRIDE /
   LOCAL / SEEDED / OK. If everything is OK: one line, done.
3. **(C1)** Append one adhoc METRICS line — you, the orchestrator, never the tool (single-writer,
   Law 3) — to `docs/metrics/adhoc-<yyyy-MM>.jsonl`:
   `{"v":1,"t":"<utc>","evt":"kit-verify","kitVersion":"<installed>","ok":N,"modified":N,"conflict":N,"stale":N,"override":N}`
4. Never auto-fix. Report-only is the design (Law 11 — on the loop, not in it). A MODIFIED finding
   is *evidence*; re-bootstrapping over it destroys the evidence. The human chooses the exit.

## When to run

After any re-bootstrap; when a project misbehaves in ways that smell like methodology drift
(sweeps failing oddly, an agent behaving off-spec); before filing a kit bug (rule out a local fork
first); periodically on long-running projects.