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/ship-feature/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: ship-feature
+description: Implement a feature safely end-to-end in this repository. Use when adding or changing functionality across backend, frontend, or MCP with required verification and documentation updates.
+---
+
+# Ship Feature
+
+Use this workflow for medium or large implementation tasks.
+
+## Steps
+- Explore impacted modules first.
+- Write a short implementation plan before editing.
+- Implement smallest coherent diff that satisfies requirements.
+- Run relevant verification commands.
+- Update docs when commands, paths, architecture, or behavior changed.
+
+## Required quality checks
+- Keep API and websocket contracts stable unless intentionally changed.
+- Keep destructive operations behind explicit guardrails.
+- Avoid broad refactors in feature tickets unless requested.
+
+## Finish checklist
+- Tests/build/typecheck completed or explicitly reported as not run.
+- Changed file set is scoped and intentional.
+- User-facing docs updated if behavior changed.
+
+## References
+- Checklist template: `references/feature-checklist.md`