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-devtools/commands/export.md

@@ -0,0 +1,30 @@
+---
+description: Export Agent Monitor data (sessions/events/analytics/costs/all) as json/csv/md.
+argument-hint: "[sessions|events|analytics|costs|all] [json|csv|md]"
+---
+
+Export Agent Monitor data using the dashboard export endpoint. Arguments:
+**$ARGUMENTS** — the first token is the data `type`, the second is the `format`.
+
+- `type` ∈ `sessions | events | analytics | costs | all` (default `all`)
+- `format` ∈ `json | csv | md` (default `json`)
+
+Set `TYPE` and `FORMAT` from the args (apply the defaults if missing), then run:
+
+```bash
+TYPE="${1:-all}"; FORMAT="${2:-json}"
+curl -s "http://localhost:4820/api/settings/export?type=${TYPE}&format=${FORMAT}" \
+  -o "ccam-export-${TYPE}.${FORMAT}"
+```
+
+Then:
+1. Confirm the file was written and report its absolute path and byte size.
+2. Preview the result: for `csv`/`md` print the first ~15 lines; for `json`
+   print a pretty-printed head (e.g. `head -c 1500` or the first array element
+   plus the record count).
+3. Print a one-line summary: `Exported <type> as <format> → <path> (<N> records / <bytes>)`.
+
+If the curl returns a non-200 or an error body, do not claim success — print the
+error and remind the user to start the dashboard with `npm start` from the repo
+root. Do not delete or overwrite any existing data; this command only reads via
+the export endpoint and writes a new export file.