Users are reporting issues where after the state expires on the backend, if their socket reconnects, the old state lingers in the client until they send some other event which triggers a reload, which triggers a rehydrate.

The new behavior should be to always reload when reconnecting if the target state has no router_data. ie: on socket connect, if we have seen the token before, but the state is new, emit a reload event and let the frontend take care of rehydrating.