Get Hooks Diagnostics

34f76536 — live hook-configuration diagnostics for the active repo.

Surfaces hook_paths.diagnose_configured_hooks as a real endpoint instead of logic that only tests ever exercised. Classifies every hook command configured in the active repo's .claude/settings.json as ok / a genuine missing REQUIRED project hook ($CLAUDE_PROJECT_DIR-scoped, must exist in this repo) / an OPTIONAL global hook that is legitimately absent until the user runs the hooks.ps1/hooks.sh installer on this machine / unresolvable. A missing OPTIONAL hook is never treated as a problem here -- only missing_required_count signals a genuine, actionable misconfiguration.

Never raises: an absent or unreadable settings.json yields settings_found: false with an empty hooks list rather than a 404/500, since a diagnostics endpoint must never itself become a source of failure for a session that polls it during orientation.

55d48d69 -- guard reports the Meridian guard: whether it is registered, whether every registered shim's runtime resolves, the effective mode (off / advisory / enforce, from MERIDIAN_GUARD and the owner's sentinel files) and the disabled rules. status folds that into one word: not_installed, off, runtime_missing, advisory or enforce. The guard fails open when its runtime is missing, so this is where a broken install shows up. Mode and runtime are computed from THIS server process's environment, which can differ from the Claude Code session that runs the hooks.

get/hooks/diagnostics

Request

  • Base URL: https://usemeridian.us (the document declares no server; this is the origin it was published from)
  • URL: https://usemeridian.us/hooks/diagnostics
  • Auth: none declared

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.