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.

.agents/skills/release-guard/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: release-guard
+description: Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
+---
+
+# Release Guard Skill
+
+## Workflow
+- Check command consistency across docs and `package.json`.
+- Verify architecture docs align with current code paths.
+- Validate that safety controls are still documented and enforced.
+- Report pass/fail with concrete file references.
+
+## Focus areas
+- Hook flow and failure behavior.
+- Session/agent lifecycle semantics.
+- MCP safety gates and host setup instructions.
+- Troubleshooting accuracy.
+
+## References
+- `references/release-checklist.md`

.agents/skills/release-guard/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Release Guard"
+  short_description: "Audit release readiness across code, docs, and safety controls."
+  default_prompt: "Use release-guard to audit this branch for release readiness and report concrete findings."

.agents/skills/release-guard/references/release-checklist.md

@@ -0,0 +1,7 @@
+# Release Checklist
+
+- Commands in docs exist in root `package.json`.
+- Validation steps are documented for backend, frontend, and MCP.
+- Behavior-changing diffs mention migration/compatibility impacts.
+- Safety-sensitive operations remain guarded by explicit flags.
+- Troubleshooting sections reflect the current architecture.