Windsurf rules

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