Undelivered wrap-up warnings and user-queued messages survived abort() in the steering/followUp queues; the SDK post-run handler treated them as continuation intent and resurrected the task for another full duration window, with waitForIdle never settling. The deadline path now clears both queues before aborting (session.clearQueue semantics), records warningDelivered and droppedQueuedMessages in the timeout marker for observability, and exposes a clear_queued_messages worker command so spawned/sandbox backends share the same sequence.