Notifications sent from a remote session now actually reach you instead of being silently discarded.
What's wrong with this entry?
notification frames arriving on the remote and thin-client streams used to be dropped on the floor; they now reach the local notification queue.
- frames are validated for a string key, string text and a known priority; malformed frames are dropped with a debug line
- normalisation prefixes the key with
remote:, collapses text to a single line, downgradesimmediatepriority tohighand clamps the timeout - an older remote notification is evicted when the remote quota is full
- telemetry records the routing path taken
tengu_remote_notification_routed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.