dw-doctorlisted

# dw-doctor — read-only environment diagnostic Confirm the machine actually has what this repo's hooks and skills assume, and that the wiring resolves — before a missing tool silently degrades things. The sharpest case: every `.claude/hooks/*.sh` opens with `command -v jq >/dev/null || exit 0`, so on a box without `jq` the dangerous-command block, `.env` protection, pnpm enforcement, and lint/typecheck-on-edit hooks **all quietly no-op** and nobody notices. Same failure class for a missing `pnpm`, a `settings.json` pointing at a hook that isn't executable, or a typecheck hook with no `tsc` to call. **Read-only:** it probes (`command -v`, `--version`) and reads files, then reports. It never installs a tool, never edits a file, never runs the fixes it suggests — applying them is your call. The version probes deliberately run from `/`, not from the repo: `pnpm -v` and `node -v` inside a repo declaring `devEngines` resolve that declaration, download a runtime to satisfy it and rewrite `pnpm-lock.yaml` — and then answer with the pinned version, so the check would compare the pin against itself. From outside, the answer is the tool on PATH, which is what "is the pin in effect?" is asking about. ## What it reads It diagnoses the **current git repo** (resolved via `git rev-parse --show-toplevel`), not the skill's own location. Checks are conditional on what the repo declares, so nothing about a stack is assumed: - `package.json` — the Node pin (`devEngines.runtime` first, then `