Session lifecycle
Connected, ready and playing are three different states.
Start
The client opens a loopback WebSocket and sends client.hello first, using its launch manifest. An accepted server.hello provides capabilities. Connect resolves; the application loads assets and sends game.ready. Only session.start authorizes the game session. Countdown is a value; the application displays it and blocks input until it expires.
Run
session.pause freezes active time, input and dependent animations. Heartbeat continues. session.resume removes the pause without resetting scores. device.state describes the device; Launcher owns hardware interlocks, not the game.
End
Natural completion sends session.complete once. session.stop commands the game to stop; it does not mean automatically recording a victory. After transport loss the client never restores the old session. Another launch requires a new Launcher decision and manifest. Sending complete is not a separate confirmation that Cloud stored the result.