Never miss the signal.

1. 1

   Socket live: subscribe

   The bell and thread views subscribe to Realtime channels; new rows arrive with chime and badge, no refresh needed.
2. 2

   Socket down: poll

   If the connection drops, both surfaces fall back to periodic refresh per the fail-open axiom — drafts and read state stay local until the socket returns.
3. 3

   Unmount: clean up

   Channels terminate on unmount. Dangling sockets are a memory leak with a chat UI attached — close them.

The lead's raid call carries an action URL straight into the squad thread, so members tap once and land in the war room. The render ping arrives mid raid without breaking focus, and the moved card closes the loop on the squad kanban board. When ten events fire in a minute, the 5 second rate limiter folds them into calm badges instead of a chime avalanche. Squad setup lives in squad workspaces.

1. 1

   Bell rings for nothing, or nothing rings

   Confirm the Realtime channel is subscribed, then check the storm window: bursts inside 5 seconds collapse into one badge by design. If the bell is empty after reconnect, pull to refresh once, the fail-open poller backfills what the socket missed.
2. 2

   Messages refuse to send

   Verify thread membership: inserts require the sender to be a participant, and archived squad threads lock to read only. Ask a lead to re-add you, then resend.
3. 3

   Badge count looks wrong

   Mark-read touches your row alone, so a stale badge means the write raced the poller. Open the notification center once to settle it; a count that survives that is a bug worth reporting with the category and timestamp.