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-productivity/commands/whats-next.md

@@ -0,0 +1,20 @@
+---
+description: Suggest the next action from your most recent in-progress sessions and recent errors.
+argument-hint: "[project-path]"
+---
+
+Recommend what to pick up next, using Agent Monitor data at `http://localhost:4820`. If the dashboard is unreachable, tell the user to start it with `npm start` from the repo root.
+
+Optional **$ARGUMENTS**: a project path (`cwd`) to scope the suggestion to one project; otherwise consider all recent work.
+
+1. Fetch recent sessions: `curl -s 'http://localhost:4820/api/sessions?limit=20'` (already sorted most-recently-updated first).
+2. For the most recent unfinished sessions (`status` of `running`, `error`, or `abandoned`), fetch their events to see where they left off:
+   `curl -s 'http://localhost:4820/api/events?session_id=<id>'` — look at the last few events (last `tool_name`, `summary`, and any `APIError` / `Compaction` event types).
+
+Print a short, prioritized "Next up" list (top 3–5 items). For each item give:
+
+- The project (`cwd`) and session status.
+- What it was last doing (from the final events / last tool used).
+- A concrete suggested next action (resume, debug the error, re-run after compaction, or close out).
+
+Put unresolved errors and abandoned-mid-task sessions at the top. Keep it to one screen and cite only data returned by the API.