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.
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
name: mcp-maintainer
|
||||
description: Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
|
||||
---
|
||||
|
||||
# MCP Maintainer Skill
|
||||
|
||||
## Workflow
|
||||
- Confirm dashboard API availability (`/api/health`).
|
||||
- Inspect affected MCP domain modules under `mcp/src/tools/domains/`.
|
||||
- Preserve safety gates in `mcp/src/policy/tool-guards.ts`.
|
||||
- Validate with `npm run mcp:typecheck` and `npm run mcp:build`.
|
||||
|
||||
## Safety rules
|
||||
- Keep loopback-only target checks enabled.
|
||||
- Keep mutating and destructive tools behind explicit flags.
|
||||
- Do not log protocol data to stdout.
|
||||
|
||||
## References
|
||||
- `references/tool-domain-map.md`
|
||||
- `references/operations-runbook.md`
|
||||
@@ -0,0 +1,4 @@
|
||||
interface:
|
||||
display_name: "MCP Maintainer"
|
||||
short_description: "Maintain MCP tools, policy gates, and host integration."
|
||||
default_prompt: "Use mcp-maintainer to update MCP tooling safely and verify runtime integrity."
|
||||
@@ -0,0 +1,14 @@
|
||||
# MCP Operations Runbook
|
||||
|
||||
## Modes
|
||||
- Read-only:
|
||||
- `MCP_DASHBOARD_ALLOW_MUTATIONS=false`
|
||||
- `MCP_DASHBOARD_ALLOW_DESTRUCTIVE=false`
|
||||
- Admin:
|
||||
- Set mutations true for controlled maintenance operations.
|
||||
- Destructive:
|
||||
- Set both true and require `confirmation_token = CLEAR_ALL_DATA`.
|
||||
|
||||
## Verification
|
||||
- `npm run mcp:typecheck`
|
||||
- `npm run mcp:build`
|
||||
@@ -0,0 +1,8 @@
|
||||
# MCP Tool Domain Map
|
||||
|
||||
- `observability-tools.ts`: health, stats, analytics, snapshots, export.
|
||||
- `session-tools.ts`: list/get/create/update sessions.
|
||||
- `agent-tools.ts`: list/get/create/update agents.
|
||||
- `event-tools.ts`: event listing and hook ingestion.
|
||||
- `pricing-tools.ts`: pricing CRUD and cost calculations.
|
||||
- `maintenance-tools.ts`: cleanup, reimport, reinstall hooks, destructive clear.
|
||||
Reference in New Issue
Block a user