Attaching to a cloud session with an unknown or malformed id is refused immediately with a message.
What's wrong with this entry?
Attaching to a remote session used to log a failed lookup and carry on over the websocket anyway. An unknown session id or a malformed one is now refused outright with a message saying so; other lookup errors still fall through to the websocket as before.
- The refusal records a
tengu_remote_attach_session_rejectedevent carrying the reason.
cloud attach refused: the id names no session of this account, or is malformed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.