Cursor rule

1---
2description: "Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel."
3alwaysApply: false
4---
5 
6# Visual Dashboard
7> **HARD GATE** — **HARD GATE** — Dashboards are read-only. Do NOT use visualization to make decisions without consulting the source data. 'The chart looks better' is not a decision.
8 
9 
10Browser-based visual companion for bigpowers. Visualizes architecture, plans, and status.
11 
12## HTTP cockpit (YAML SoT)
13 
14Start the server:
15 
16```bash
17bash visual-dashboard/scripts/start-server.sh
18```
19 
20Endpoints:
21 
22| Route | Purpose |
23|-------|---------|
24| `GET /api/status?projectDir=<abs>` | JSON: `state`, `release`, `epics[]`, `planning_status`, `active_epic` |
25| `GET /cockpit.html?projectDir=<abs>` | Read-only PM view (planning left, epics right) |
26| `GET /` | Agent-pushed HTML screens (legacy, unchanged) |
27 
28Example:
29 
30```bash
31curl -s &quot;http://127.0.0.1:PORT/api/status?projectDir=$PWD&quot; | jq .release.version
32```
33 
34Implementation: `visual-dashboard/scripts/read-specs-status.cjs` + `server.cjs`.
35 
36## Opencode Progress Panel
37 
38Projects using bigpowers in opencode can read `specs/state.yaml`, `specs/release-plan.yaml`, and active `specs/epics/*.yaml` directly (no checkbox `### WS1` markdown).
39 
40Required YAML keys:
41 
42- **state.yaml** — `active_flow`, `active_epic_id`, `git`, `handoff`, `epic_cycle`
43- **release-plan.yaml** — `release.version`, `epics[]` with `id`, `title`, `wsjf`, `file`
44- **execution-status.yaml** — `development_status` map (story/epic → `done` | `pending`)
45- **planning-status.yaml** — discover workflows and `status: done|pending`
46 
47## Agent screens (optional)
48 
49Push HTML to the dashboard session dir for rich diagrams. See `start-server.sh` for `CONTENT_DIR`.
50