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.

.claude/skills/debug-live-issue/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: debug-live-issue
+description: Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
+---
+
+# Debug Live Issue
+
+Use this workflow for incident-style debugging.
+
+## Steps
+- Capture symptom, expected behavior, and reproducible path.
+- Isolate subsystem first: hook ingestion, API route, DB state, websocket, or UI rendering.
+- Reproduce with minimal surface area.
+- Prove root cause before changing code.
+- Apply minimal fix and re-verify.
+
+## Evidence standards
+- Prefer direct logs, API responses, DB state checks, and deterministic repro steps.
+- Avoid speculative fixes without root-cause evidence.
+- If not fully reproducible, state uncertainty and strongest hypothesis.
+
+## References
+- Investigation template: `references/investigation-template.md`