Group of 3 You'll notice
Queued notification messages are relayed through Remote Control but get dropped with a warning if there's no remote transport to route them to
What
- The Remote Control REPL bridge now relays queued notifications into the app during a bridge session, using the same handler as before.
- An incoming
queued_notificationcontrol message is now dropped (and not acknowledged) unless the session is using a remote transport, logging a warning and recording a new telemetry reason. - The warning text shown when a queued notification has nowhere to go was reworded from referencing "remote mode" to referencing a missing "ingress host".
Why
This ensures queued notifications are only delivered when there's an actual remote connection able to receive them, and makes the failure message clearer about why a notification was dropped.