Queued commands can now be marked cancelled when an interrupt sweeps the queue.
What's wrong with this entry?
The internal schema description for queued-command lifecycle states documents a new way a command reaches 'cancelled' and tells exactly-once resenders how to reconcile against it.
- New cause for 'cancelled': the command was swept by an interrupt carrying cancel_queued:true
- Resenders should reconcile against the interrupt receipt's
cancelledlist in addition to their own cancel_async_message responses before resending - The named receipt capability string is new in this build
swept by an interrupt with cancel_queued:true
Strings lifted out of the shipped bundle, so the claim above can be checked against them.