Lifecycle of the receive event stream (0.30.0) — observable via
client.streamState + onStreamStateChange, so a host can render a
connection indicator without hand-rolling its own enum.
idle — before start()
connecting — start() called; first connection being established
connected — the event stream is live (WS or SSE as configured)
reconnecting— connection lost / closed; backing off before the next try
degraded_sse— the WebSocket transport errored and delivery continues on
the SSE fallback (still live — replies keep arriving)
stopped — stop()/close() was called, or a permanent stream failure
(the stream_unauthorized control.error) ended the loop
Lifecycle of the receive event stream (0.30.0) — observable via
client.streamState+onStreamStateChange, so a host can render a connection indicator without hand-rolling its own enum.idle— before start()connecting— start() called; first connection being establishedconnected— the event stream is live (WS or SSE as configured)reconnecting— connection lost / closed; backing off before the next trydegraded_sse— the WebSocket transport errored and delivery continues on the SSE fallback (still live — replies keep arriving)stopped— stop()/close() was called, or a permanent stream failure (thestream_unauthorizedcontrol.error) ended the loop