Round-2 follow-up. Two small holes flagged by the adversarial review of
the connection-diff-loop projector:
- A projector that starts throwing only after a shape regression would
wedge the diff baseline silently — no publishes, no log, the only
symptom is the dashboard's connections card freezing until restart.
Latch a one-shot console.error on the first throw so the failure is
visible without re-running the loop locally.
- The non-array fallback at the projector site in server.ts returned
`acc.adapters` verbatim, which would re-introduce volatile fields if
the snapshot shape ever drifts. Tighten to `[]`.
Also documented the deliberate trade-off: per-second adapter `detail`
rotation (client count, last-delivery HH:MM:SS) refreshes on the next
SSE push or the 30s REST reconcile rather than in real time. The user's
original bugs were about process/account edges (which DO push
instantly); detail-string freshness was not in scope. If it becomes one,
surface client-count as a structured AdapterStatus field instead of
parsing the localised `detail`.
437/437 core green.