Idle notices from other sessions now wait their turn behind earlier peer messages.
What's wrong with this entry?
Idle notifications used to take the fast out-of-band path used by all control messages between sessions; they now go through the ordered processing chain instead, so an idle notice cannot overtake peer messages queued before it.
- Only the idle-notice action is excluded from the fast path; other control messages still use it.
- Reachable when cross-session peer messaging is in use.
(e.type === "control" && e.action !== "notify_when_idle")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Wake routing and cross-session notices rewritten off UI effects
Both mention multi
-
v2.1.246
Multi-agent reply pairing now rejects and counts suspicious matches
Both mention multi
-
v2.1.239
Worker agents told to review, test, commit and report a PR link
Both mention multi