What
The control-protocol schema now explains what happens to a message a client is still holding back: a plain interrupt leaves it held and lists it under still_queued, while cancelling queued messages withdraws it and reports it under cancelled.
Details
- The same message can also be withdrawn on its own with
cancel_async_message. - Today the only such hold is a message waiting for the session to take the initial upload from that machine.
- A hosted-session driver follows a cancellation with a
command_lifecycleframe markedcancelledwhen its own sweep cancels a send it had already delivered. - The behaviour is advertised to clients through the
interrupt_cancel_queued_v1capability.
Evidence
behind a send gate (today: waiting for the session to take the initial upload from that machine)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.