Observability 3: boards are live by streaming per-panel points, never by re-fetching HTML #3692

Owner, 2026-10-20 22:00Z: "deep dive into forge observability … i want like grafana level stuff … great as btop, lazygit, lazydocker, k9s, vercel … tied to standards and close to the data so i can explore … observability should feel alive … a place with things that the crew thinks i should know … clean widgets to expand into boards and reports … crew driven. engaging and fun. gamified. but still high utility. high signal to noise. if its quiet, fine! dont just spam me to fill the box." Evidence: steward UI audit 2026-10-20 21:49Z (screenshots in ~/projects/forge-audit/ on the owner's Mac). Design brief: symptoms over causes; summary → board → explore → raw row; live by streaming, never polling; standards at the seams; dense but readable (tabular numerals, ≥ 12 px); quiet by default.

Done: boards are live by streaming deltas: one SSE (or the existing /events) carries per-panel new points; the page appends them — no HTML re-fetch. Today /boards/:slug/live returns 439 KB of HTML in 1.6 s per event, 5–7 times in 12 s, most aborted; the /boards index has no live updates. Show "live · updated Ns ago" and a paused state. Test: a new data point reaches an open board within 2 s with < 2 KB on the wire; no request repeats while idle.

Parked by the crew: the check failed ("design check: nothing added outside the system (#2678) > the tree is no worse than its baseline") and the decider saw no point in another try (pull #3714 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.