Work done locally for a cloud session that never arrived now gets its own explanatory message.
What's wrong with this entry?
When work this machine did for a cloud session fails to arrive, you now see text saying the result of that work, a command it ran or files it synced, did not reach the session before it stopped waiting.
- Previously only hook responses had an undelivered explanation; tool responses now have their own.
- Cancelling a request now gives up on in-flight tool responses as overtaken, matching how hooks were already handled.
The result of work this machine did for the cloud session (a command it ran, or files it synced) did not reach the session before it stopped waiting for it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.