Previous audit allowed up to 5 requests in a 30s window — generous,
hid real regressions. Tighten:
- 5s settle after each scene becomes interactive (covers the burst
of mount-time fetches every scene legitimately fires)
- 55s observation window after settle, sized to fit between two
consecutive 60s topbar badge polls
- MAX_REQ_PER_WINDOW = 0; any /api/* or /internal/* request during
the window fails the assertion
This is the operator-experience contract: when you stop typing,
canvas stops fetching.
Idle-poll audit caught a regression I introduced in the prior commit:
the topbar badge poll iterated chatApi.listMessages per thread on each
60s tick, firing N requests per refresh. Landing scene showed 9 reqs
in a 30s idle window (failed the <=5 budget).
Now the topbar badge just shows the THREAD COUNT (not per-thread
unread), which is a single chatApi.listThreads call. Per-thread unread
math stays in the Chat scene where it belongs (already wired:
chat-thread-row.unread + .chat-unread-summary).
canvas-bot
shad