diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md index 5d827a8c..028892ea 100644 --- a/docs/web-ui/dashboard.md +++ b/docs/web-ui/dashboard.md @@ -228,16 +228,18 @@ not the graph. **R3BU1LD QU3U3** — pending, in-flight, and recently-settled container operations: rebuilds, meta-update cascades, and first-spawns. One operation runs at a time; the worker drains FIFO. **Is a mounted -``** (the shared generic -graph-viewer component, `@hive/shared/jobq-graph.js`) — `builds.js` -does not render the queue itself; it just mounts the element and -listens for its `hive-jobq-graph-update` event to drive the two things -below it that the generic view doesn't show. The component owns -fetching, cold and live: `GET /api/jobq/graph` on mount, and -`.refresh()` on every `rebuild_queue_changed` SSE tick (that event is a -bare `{ seq }` trigger — it carried a typed queue snapshot until every -consumer had moved to the generic endpoint, and now carries none; both -dashboard pages treat the tick as a pure refetch trigger). +`JobqGraph`** (the shared generic graph-viewer Preact component, +`@hive/shared/jobq-graph.js` — the same one swarm-ui uses, a Preact port +of the former shadow-DOM `` custom element) — `builds.js` +does not render the queue itself; it just mounts the component +(`mountJobqGraph(container, props)`, since this page has no JSX +pipeline) with an `onUpdate` callback to drive the two things below it +that the generic view doesn't show. The component owns fetching, cold +and live: `GET /api/jobq/graph` on mount, and a refetch via the mount +handle's `.refresh()` on every `rebuild_queue_changed` SSE tick (that +event is a bare `{ seq }` trigger — it carried a typed queue snapshot +until every consumer had moved to the generic endpoint, and now carries +none; both dashboard pages treat the tick as a pure refetch trigger). Each row is one root graph node (`parent: null`); a multi-step op's per-agent subgraphs and sub-steps render as nodes within that one @@ -250,10 +252,10 @@ as a plain "waits on: `