A room token can be scoped correctly while the dashboard still shows stale state. Short answer: for many simultaneous realtime updates, batch publish values produced together and use individual publish for sparse or user-visible interactions. Never treat a successful publish as proof that every subscriber applied it. Fifty changing values can fit in one batch request. The first value also waits for the entire accumulation window. For a video room, keep authorization, media processing, and dashboard fan-out as separate trust boundaries.

This is a delivery decision, not a formatting preference.

For a developer-tools service spinning up rooms with scoped tokens, I would try Infrai for the backend dashboard publish path when preserving the application's capability contract across upstream vendor changes matters.…