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/focus-report.md

@@ -0,0 +1,19 @@
+---
+description: One-screen focus snapshot — avg turn duration, thinking-block usage, and longest sessions.
+argument-hint: "[limit]"
+---
+
+Print a one-screen focus snapshot from 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 session count to inspect (default 100).
+
+1. Fetch sessions: `curl -s 'http://localhost:4820/api/sessions?limit=100'` (use the $ARGUMENTS limit if given). Parse each `metadata` JSON for `turn_count`, `total_turn_duration_ms`, and `thinking_blocks`.
+2. Fetch baselines: `curl -s http://localhost:4820/api/analytics` for `avg_events_per_session` and `sessions_by_status`.
+
+Compute and print (over sessions that have the focus metadata):
+
+- **Avg turn duration** = `total_turn_duration_ms / turn_count`, reported in seconds (averaged across sessions).
+- **Thinking-block usage** = average `thinking_blocks` per session and per turn (`thinking_blocks / turn_count`).
+- **Longest sessions**: top 3–5 by `total_turn_duration_ms`, each with project (`cwd`), duration in minutes, turn count, and thinking blocks.
+
+Show the three metrics as a compact table plus the longest-sessions list. State how many sessions had usable metadata. Durations from ms; cite only numbers returned by the API. Keep it to one screen.

plugins/ccam-productivity/commands/standup.md

@@ -0,0 +1,22 @@
+---
+description: Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
+argument-hint: "[today|yesterday]"
+---
+
+Generate a fast daily standup from Agent Monitor data at `http://localhost:4820`.
+
+Target day from **$ARGUMENTS**: "today" or empty = the last calendar day; "yesterday" = the day before. If the dashboard is unreachable, tell the user to start it with `npm start` from the repo root.
+
+1. Fetch sessions:
+   `curl -s 'http://localhost:4820/api/sessions?limit=50'`
+   Keep sessions whose `started_at` falls on the target day.
+2. Fetch cost: `curl -s http://localhost:4820/api/pricing/cost` for the `total_cost` and per-model `breakdown`.
+
+Print a compact standup (aim for a 30-second read):
+
+- **One-line summary** suitable for pasting into Slack (e.g. "5 sessions across 3 projects, 4 done, $0.7421").
+- **Done / In progress** grouped by project (`cwd`): per group list session count and statuses (`completed`, `running`, `error`, `abandoned`).
+- **Errors / blockers**: any session with `status` `error` or `abandoned`; name the project.
+- **Numbers**: total sessions, completion rate (completed / total), and estimated cost in USD to 4 decimals.
+
+Keep it terse — this is a one-shot, not a full report. Cite only numbers returned by the API.

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.