doctorlisted

# /foundry:doctor The Foundry self-diagnostic — a **thin, five-check probe** (the v0.25.0 test-suite realignment; `foundry-doctor.py` shrank from a 2,900-line drop-in-check registry, `--selftest` CLIs and all, to one file). The load-bearing behavioral assertions this file used to re-discover from the retired per-check registry now live in the **one pytest suite** (`tests/`), run by CI on every PR — `foundry-doctor.py` is a cheap, fast, every-session-safe probe, not the enforcement floor. The **real merge-side enforcement** is the native floor (`.github/workflows/ci.yml` + the `btb-gates` lane signal — Tier B advisory) plus `hooks/foundry-git-discipline.sh`'s deterministic `gh` clause. `doctor` is a mistake-catcher for the operator, not a merge gate. ## When to trigger - Operator: "/foundry:doctor", "is Foundry healthy?", "why does my session look off?". - After editing `hooks/hooks.json`, any `skills/*/SKILL.md` frontmatter, or a stack-profile lock. - Before a release, as a cheap sanity pass (the binding pre-cut gate is `foundry-release-acceptance.py`, which itself requires `DOCTOR-GREEN` — see `skills/release/SKILL.md`'s pre-cut acceptance gate). ## Procedure 1. **Run the doctor**: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/foundry-doctor.py" ``` The five checks, every run: 1. **`manifest`** — `.claude-plugin/plugin.json` loads as JSON and carries a `version`. 2. **`hooks`** — `hooks/hooks.json` parses as JSON and every referenced hook command