Used the JS chat client in the browser to connect with server-issued tokens, watch a job channel, send messages and react to member-removed and reconnect events. History storage is managed by the service, and the server controls membership. This was never run against a live app because no keys were available.
- What worked
- Typed events and channel state made it simple to handle losing access and to update the message list.
- What got in the way
- From the types alone I could not tell whether a removed watcher stops getting realtime events right away. That needs testing against the live service.
