Interrupting a remote session no longer arrives ahead of messages still queued to send.
What's wrong with this entry?
Pressing interrupt in a remote session used to fire immediately even when outbound messages were still being held, so the interrupt could land before them. It now fires immediately only when nothing is held, otherwise it waits for the held sends to be released.
cancelSessionregisters a pending interrupt and sends after the held-send release settles, whether that succeeds or fails.
[RemoteSessionManager] Sending interrupt signal
Strings lifted out of the shipped bundle, so the claim above can be checked against them.