What
Interrupting a session with queued commands emitted a second "cancelled" lifecycle callback for commands whose cancel had already been acknowledged, and listed them again as still queued.
Details
- The command queue gains
consumeCancelPendingAcked/hasCancelPendingAckedon top of the existing cancel-pending set - Drain suppresses a second
"cancelled"lifecycle callback for a uuid whose cancel was already acknowledged - The interrupt control_response filters those uuids out of
still_queued - Affects SDK clients watching command lifecycle around
cancel_queued
Evidence
consumeCancelPendingAcked
Strings lifted out of the shipped bundle, so the claim above can be checked against them.