---
description: Diagnose a plugin-installed CCAM — Node, bootstrap, server, hooks, CLI, MCP build
---

Run the diagnostic and report what it found. Do not fix anything unless the user
asks.

```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-doctor.js"
```

Print the output verbatim, then add at most three lines of guidance based on the
`FAIL` and `WARN` rows:

- `FAIL Node` → the installed Node is too old for `node:sqlite`; the server
  cannot start until Node is upgraded.
- `FAIL Hooks` → duplicate hook entries double every token and cost figure.
  Starting a new Claude Code session removes them automatically (the bootstrap
  backs the file up as `settings.json.ccam-bak` first).
- `FAIL Server` or `FAIL Runtime deps` → run `/ccam-update`, then check
  `~/.claude/agent-dashboard/runtime/bootstrap.log` and `server.log`.
- `FAIL MCP build` → `mcp/build/` is out of date; run `npm run mcp:build` in a
  checkout and commit it.
- `WARN ccam CLI` → print the exact `export PATH=...` line from the output.
- `WARN Dashboard UI` → run `/ccam-open` to build the bundle.

No preamble, no summary of things that passed.
