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,26 @@
|
||||
---
|
||||
name: repo-onboarding
|
||||
description: Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and verification strategy before coding.
|
||||
---
|
||||
|
||||
# Repo Onboarding
|
||||
|
||||
Use this workflow when a task begins with discovery.
|
||||
|
||||
## Steps
|
||||
- Read `README.md` and `ARCHITECTURE.md` for system-level context.
|
||||
- Identify target layer:
|
||||
- `server/` for API, hooks, DB, websocket
|
||||
- `client/` for UI and routing
|
||||
- `mcp/` for local MCP tools and policy gates
|
||||
- Select the smallest set of files required to answer the task.
|
||||
- Confirm verification commands before implementation.
|
||||
|
||||
## Verification defaults
|
||||
- Backend: `npm run test:server`
|
||||
- Frontend: `npm run test:client`
|
||||
- MCP: `npm run mcp:typecheck` and `npm run mcp:build`
|
||||
|
||||
## References
|
||||
- Module map: `references/module-map.md`
|
||||
- Command map: `references/command-map.md`
|
||||
@@ -0,0 +1,25 @@
|
||||
# Command Map
|
||||
|
||||
## Root commands
|
||||
- `npm run setup`
|
||||
- `npm run dev`
|
||||
- `npm run build`
|
||||
- `npm start`
|
||||
- `npm run test:server`
|
||||
- `npm run test:client`
|
||||
- `npm run install-hooks`
|
||||
- `npm run import-history`
|
||||
- `npm run clear-data`
|
||||
|
||||
## MCP helper commands (root)
|
||||
- `npm run mcp:install`
|
||||
- `npm run mcp:build`
|
||||
- `npm run mcp:start`
|
||||
- `npm run mcp:dev`
|
||||
- `npm run mcp:typecheck`
|
||||
|
||||
## Direct MCP package commands
|
||||
- `npm --prefix mcp install`
|
||||
- `npm --prefix mcp run build`
|
||||
- `npm --prefix mcp run start`
|
||||
- `npm --prefix mcp run typecheck`
|
||||
@@ -0,0 +1,20 @@
|
||||
# Module Map
|
||||
|
||||
## Backend
|
||||
- `server/index.js`: app composition, startup behavior, periodic maintenance.
|
||||
- `server/db.js`: schema and prepared statement ownership.
|
||||
- `server/routes/*.js`: endpoint contracts by domain.
|
||||
- `server/websocket.js`: WS lifecycle and broadcast behavior.
|
||||
|
||||
## Frontend
|
||||
- `client/src/pages/`: route-level screens.
|
||||
- `client/src/components/`: reusable UI building blocks.
|
||||
- `client/src/lib/api.ts`: client API access patterns.
|
||||
- `client/src/hooks/useWebSocket.ts`: live update pipeline.
|
||||
|
||||
## MCP
|
||||
- `mcp/src/index.ts`: runtime entrypoint.
|
||||
- `mcp/src/server.ts`: MCP assembly.
|
||||
- `mcp/src/tools/domains/`: domain tool registration.
|
||||
- `mcp/src/clients/dashboard-api-client.ts`: resilient API bridge.
|
||||
- `mcp/src/policy/tool-guards.ts`: mutation/destructive gates.
|
||||
Reference in New Issue
Block a user