Cloud sessions now report turn start, progress and end to the environment manager.
What's wrong with this entry?
The hook that drives a remote (cloud) session builds an environment-manager driver and notifies it as frames arrive from the stream: turn-in-flight on assistant, stream-event and requesting-status frames and on every tool-progress frame, worker-init on the init frame, and turn-ended on a result frame.
- These lifecycle notifications already existed in 2.1.246; what is new is that the remote session stream drives them, so the cloud environment manager sees turn activity.
- The driver is only constructed when two conditions pass and the session is not viewer-only. The two conditions are not tied to any named flag or setting in the build, so whether the driver exists for a given cloud session is decided by that unnamed logic.
onTurnInFlight
Strings lifted out of the shipped bundle, so the claim above can be checked against them.