feat: Claude Code Monitor — lanes, pipelines and a merged workspace

Internal SmartGift build of a Claude Code monitoring dashboard.

Lanes: a durable unit of parallel agent work, one per working directory,
tracked across session restarts. Managed lanes are git worktrees the
dashboard provisions and can reset or remove behind a three-check destroy
guard and a counted preflight; adopted lanes are directories you already
own and are never destroyable.

Pipelines: a lane moves through pipeline stages. A stage the agent declares
with evidence renders green; a stage inferred from the tool-event stream
renders dashed amber and never counts as done. Detection is forward-only
within a 30-minute window, and never writes the declared stage.

Workspace: one page at /run with a lane grid, the selected lane's pipeline,
and a full Claude console behind a disclosure.

plugins/ccam-quality/commands/errors.md

@@ -0,0 +1,28 @@
+---
+description: List the most recent APIError events with their session and a summary
+argument-hint: "[N]"
+---
+
+List the most recent Claude Code errors from the Agent Monitor dashboard at
+`http://localhost:4820`. `$ARGUMENTS` is the number of errors to show (default 10).
+
+1. Pull recent events and keep only API errors:
+   ```bash
+   curl -s http://localhost:4820/api/events?limit=300
+   ```
+   Filter the array to `event_type == "APIError"`. (If `$ARGUMENTS` is a number,
+   show that many; otherwise show 10.) If none are found, also check
+   `curl -s http://localhost:4820/api/analytics` `event_types.APIError` to confirm
+   the true total and say "no recent APIError events (N total all-time)".
+
+2. For each error, newest first, print one line:
+   `timestamp · session_id · summary` — using the `timestamp`, `session_id`, and
+   `summary` fields exactly as returned (trim long summaries to ~100 chars).
+
+3. End with a one-line tally: total APIErrors shown and the most-affected
+   `session_id`.
+
+Output rules: cite only fields the API returned — never fabricate an error or a
+cause. Keep it to the list plus the tally; no extra prose. If `curl` cannot reach
+`http://localhost:4820`, tell the user to start the dashboard with `npm start`
+from the repo root.

plugins/ccam-quality/commands/health.md

@@ -0,0 +1,31 @@
+---
+description: One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage
+---
+
+Print a single reliability verdict for Claude Code usage from the Agent Monitor
+dashboard at `http://localhost:4820`. No arguments.
+
+1. Fetch state:
+   ```bash
+   curl -s http://localhost:4820/api/stats
+   curl -s http://localhost:4820/api/analytics
+   ```
+   From `stats`: `total_events`, `events_today`, `sessions_by_status`. From
+   `analytics`: `event_types` (PreToolUse, PostToolUse, APIError).
+
+2. Derive two reliability signals:
+   - **Error rate** = `APIError / total_events` (percentage, 2 decimals).
+   - **Tool-failure rate** = `(PreToolUse − PostToolUse) / PreToolUse` (percentage).
+
+3. Pick the verdict from the worse of the two signals:
+   - **OK** — error rate ≤ 1% and tool-failure rate ≤ 1%.
+   - **DEGRADED** — either is in 1–5%.
+   - **FAILING** — either exceeds 5%.
+
+4. Print exactly one line:
+   `Reliability: <OK|DEGRADED|FAILING> — errors X.XX%, tool failures Y.YY% (N events)`
+   Prefix with ✅ (OK), ⚠️ (DEGRADED), or ❌ (FAILING).
+
+Output rules: cite only fields the API returned — never fabricate. One line only;
+no extra prose. If `curl` cannot reach `http://localhost:4820`, print
+`Reliability: UNKNOWN — dashboard unreachable; start it with \`npm start\` from the repo root.`

plugins/ccam-quality/commands/slo.md

@@ -0,0 +1,31 @@
+---
+description: Print a quick SLO snapshot — completion rate, tool success rate, and error rate
+---
+
+Print a compact SLO snapshot for Claude Code usage from the Agent Monitor
+dashboard at `http://localhost:4820`. No arguments.
+
+1. Fetch the raw counts:
+   ```bash
+   curl -s http://localhost:4820/api/analytics
+   curl -s http://localhost:4820/api/stats
+   ```
+   From `analytics`: `event_types` (PreToolUse, PostToolUse, APIError) and
+   `sessions_by_status`. From `stats`: `total_events`, `total_sessions`.
+
+2. Compute three SLIs:
+   - **Completion rate** = completed sessions / total sessions (from
+     `sessions_by_status`; exclude still-`active`/`running` sessions from the
+     denominator).
+   - **Tool success rate** = `PostToolUse / PreToolUse` (cap at 100%).
+   - **Error rate** = `APIError / total_events`.
+
+3. Compare each to its default target (completion ≥ 95%, tool success ≥ 99%,
+   error ≤ 1%) and print one line per SLI:
+   `SLI .......... observed%  (target X%)  ✅ MET | ❌ BREACHED`
+
+Output rules: rates as percentages to 2 decimals; cite only fields the API
+returned — never fabricate. End with one verdict line (e.g.,
+`SLOs: 3/3 met` or `SLOs: error rate BREACHED`). Keep it to the snapshot only; no
+extra prose. If `curl` cannot reach `http://localhost:4820`, tell the user to
+start the dashboard with `npm start` from the repo root.