What probably matters to youSection of the release
What
The control-protocol interrupt request accepts an optional cancel_queued boolean that clears queued main-thread commands along with the in-flight turn, and reports which uuids it killed.
Details
When cancel_queued === !0, every uuid-stamped main-thread command still queued, including ones dequeued for the imminent turn but not yet reachable by the abort, gets a terminal cancelled lifecycle event.
The response comes back with still_queued: [] and the cancelled uuids on a new optional cancelled field.
Without the flag, the previous still_queued behaviour is unchanged.
The capability string interrupt_cancel_queued_v1 is advertised on system/init next to interrupt_receipt_v1 and msg_lifecycle_v1, so clients can feature-detect it. None of these strings exist in v2.1.218.
The in-process SDK client's interrupt() wrapper does not send the flag, so this is for control-protocol consumers only.
Evidence
interrupt_cancel_queued_v1
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Names in the bundlecancel_queuedinterrupt_cancel_queued_v1
