The CLI now learns directly when a remote cloud worker connects or drops instead of guessing.
What's wrong with this entry?
Session update frames from the cloud were previously discarded outright. The client now reads a connection status off them and reports it, so the CLI learns when the remote worker connects or drops rather than inferring it.
- A frame with no status string is still ignored.
- If the status handler throws, the failure is logged at error level naming the handler.
[SessionsV2Client] worker connection status handler threw:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.