Local socket messages now verify which process is on the other end.
What's wrong with this entry?
The helpers that send messages and control commands over the local socket now carry an expected peer process id, verified against the connecting process along with a child-token check, and the inbox teardown and key-file state move behind an accessor. Failing to publish the inbox auth key still refuses to start an inbox.
[uds-messaging] Failed to publish the inbox auth key (refusing to run an inbox no peer can authenticate to):
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