doctor

You are running /hypo:doctor. Verify the health of the current Hypomnema wiki installation.

What this checks

• Wiki root directory exists and has hypo-config.md marker
• Required subdirectories and baseline files are present
• Claude Code hook files are installed in ~/.claude/hooks/
• ~/.claude/settings.json contains all required hook registrations
• Git repository and remote origin are configured
• No broken [[wiki-link]] references
• No overdue or missing verify_by fields on tracked pages

---

Step 1 — Resolve Hypomnema directory

Bundled scripts here run via ${CLAUDE_PLUGIN_ROOT}/scripts/. To resolve that package root: if ${CLAUDE_PLUGIN_ROOT} is already an absolute path, use it; otherwise read pkgRoot from ~/.claude/hypo-pkg.json (only when non-empty and the target script exists under it); otherwise use the hypo@hypomnema (or legacy hypomnema@hypomnema) installPath in ~/.claude/plugins/installed_plugins.json; if none resolve, stop and tell the user to run hypomnema upgrade --apply (or /hypo:upgrade on a plugin install) or reinstall instead of guessing the cache layout.

If the user specified a Hypomnema directory, pass it as --hypo-dir="<path>". Otherwise omit the flag and the script resolves the Hypomnema root automatically: HYPO_DIR env → hypo-config.md scan → ~/hypomnema default.

---

Step 2 — Run the doctor script

node ${CLAUDE_PLUGIN_ROOT}/scripts/doctor.mjs [--hypo-dir="<path>"] [--json]

• --hypo-dir=<path> — override Hypomnema root (takes precedence over HYPO_DIR env and auto-scan)
• --json — output results as a JSON array (useful for programmatic use)

---

Step 3 — Report results

Show the script output verbatim. Each line is prefixed with:

• ✓ — check passed
• ⚠ — warning (not blocking, but worth fixing)
• ✗ — failure (installation is broken)

Then show the summary line: Result: N passed, N warnings, N failed

---

Step 4 — Recommend fixes

For any ✗ failures:

• Missing Hypomnema root or required directories/files → run /hypo:init.
• 0 hook files installed → run /hypo:init.
• 0 hook registrations in settings.json → run /hypo:init.
• Hook execution smoke test failed → show the stderr excerpt in the detail verbatim; it names the cause. The repair depends on the channel, and /hypo:init is only right on one of them. If Hook files installed says "provided by the plugin loader", the install is plugin-managed and /hypo:init deliberately leaves core hooks alone: tell the user to re-install the plugin. Otherwise (npm or manual install) /hypo:init repairs an incomplete copy. When the excerpt is not a missing module, have the user run the hook directly in their shell (echo '{}' | node <the path in the detail>) and read the error there.