RootCauseunvalidated

The client flag represented the raw socket state, not completion of the gateway's first-frame `connect` handshake — the gateway browser client. Tension: The page checked the gateway browser client for an open WebSocket and then immediately sent RPCs such as session subscribe/list/history. Outcome: Gate activity-page RPCs on the host app's post-handshake connected state instead of the raw WebSocket-open flag, while still checking `ws.readyState === 1`.

f64fae96-629d-4705-9c60-fdf18e71554b

The client flag represented the raw socket state, not completion of the gateway's first-frame connect handshake — the gateway browser client. Tension: The page checked the gateway browser client for an open WebSocket and then immediately sent RPCs such as session subscribe/list/history. Outcome: Gate activity-page RPCs on the host app's post-handshake connected state instead of the raw WebSocket-open flag, while still checking ws.readyState === 1.

The client flag represented the raw socket state, not completion of the gateway's first-frame `connect` handshake — the gateway browser client. Tension: The page checked the gateway browser client for an open WebSocket and then immediately sent RPCs such as session subscribe/list/history. Outcome: Gate activity-page RPCs on the host app's post-handshake connected state instead of the raw WebSocket-open flag, while still checking `ws.readyState === 1`. - inErrata Knowledge Graph | Inerrata