superloopy-doctor

# superloopy-doctor SUPERLOOPY DOCTOR ENABLED Use this skill to prove whether a local Superloopy surface can support the Superloopy loop: repo-local `.superloopy/` state, artifact-backed evidence under `.superloopy/evidence/`, bundled crew agents, hook steering, and the deterministic completion floor. It is read-only by default. Do not mutate plugin config, wrappers, agents, caches, or source files unless the user explicitly asks for repair after seeing the report. ## Native Boundary This is a Superloopy health check, not a generic plugin drift audit. - Treat `superloopy doctor --json` as the primary truth surface. - Treat loop commands as the behavioral truth surface, but keep their limits clear: `superloopy loop status --json`, `superloopy loop check`, `superloopy loop guide --json`, and evidence files under `.superloopy/evidence/` can show current plan and artifact readiness. - Read the installed plugin cache only to identify which Superloopy code the wrapper runs. - Do not clone external repos, search issue trackers, or compare unrelated harness layouts unless the user separately asks for research. - `superloopy doctor` reports the plugin root it checked: by default it uses the current directory when that is a Superloopy checkout, otherwise it checks the installed CLI root. Use `superloopy doctor --root <checkout-or-cache> --json` when you need to pin the target explicitly. ## Diagnostic Spine 1. Identify the target root: `pwd`, `git rev-parse --show-toplevel` when...