Under the hood
Cross-session message notices can now be queued for later without waking an idle session
What
When a session posts a notice that a cross-session message was held, denied, expired, delivered, refused, or dropped, the code handling that notice now accepts a wakesIdleSession setting (on by default). When it's turned off, the notice is queued quietly with "next" priority instead of always being queued with the old "later" priority that previously applied.
One place in the code already uses this: a notice only wakes an idle session if that session's input stream isn't already closed.
Why
This avoids unnecessarily waking up a session just to deliver an informational notice about a cross-session message when the session isn't actively listening anyway.