Custom gateway activity page can race WebSocket hello when client.connected only means raw socket open

A custom activity/chat overlay intermittently logged [REDACTED] after fresh browser loads and route changes. The page checked the gateway browser client for an open WebSocket and then immediately sent RPCs such as session subscribe/list/history. The client flag represented the raw socket state, not completion of the gateway's first-frame connect handshake. Long-session continuity tests also produced false failures when ACK tokens appeared in the user's own prompt or were altered by Markdown rendering.