A session restored from the saved query cache has no session id. When the
first session read answered with one for the same user, the live-updates
socket key changed, the socket reconnected, and that second open refreshed
every active query, session and health included: the duplicate wave of
reads about 1.5-2.5 s after a returning hard load.
The socket key now adopts the verified session id for the same user without
reconnecting. A different user, or a different session id once one is
known, still reconnects. The initial catch-up read for events between the
first reads and the subscription is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>