Clients now reconnect automatically after a clean server shutdown, such as during maintenance or deployment.
Service shutdowns use the standard WebSocket close code 1012 Service Restart. After reconnecting, clients restore their desired channel subscriptions and continue receiving events without a page reload.
Explicit server disconnects and kicks still use code 4000 and remain terminal by default. Client-side disconnect() also remains terminal.
Automatic reconnect delays now include bounded jitter to prevent large groups of clients from reconnecting at the same time.