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/rules/mcp-typescript.md

@@ -0,0 +1,17 @@
+---
+paths:
+  - "mcp/src/**/*.ts"
+  - "mcp/package.json"
+  - "mcp/tsconfig.json"
+  - "mcp/.env.example"
+  - "mcp/README.md"
+---
+
+# MCP Server Rules
+
+- Keep MCP tool names stable and descriptive.
+- Keep destructive operations behind explicit guardrails.
+- Route all logs to stderr only; never write protocol logs to stdout.
+- Keep tool input schemas strict and bounded.
+- Preserve loopback-only API target enforcement unless security posture changes by request.
+- Verify MCP with `npm run mcp:typecheck` and `npm run mcp:build` after code edits.