Cancelled queued commands are reported once and no longer linger in the interrupt receipt.
What's wrong with this entry?
A queued command whose cancellation was already reported no longer produces a second cancelled event, and no longer appears as still queued in the interrupt receipt.
- the command queue gained
consumeCancelPendingAckedandhasCancelPendingAckedon top of the existing cancel-pending marks - commands whose "cancelled" lifecycle event was already emitted are skipped on later passes
- those commands are filtered out of the
still_queuedlist in the interrupt receipt sent to SDK clients
still_queued
Strings lifted out of the shipped bundle, so the claim above can be checked against them.