Text arriving over the editor bridge from peers can no longer run immediately without approval.
What's wrong with this entry?
Incoming messages on the repl bridge were always classified as ungated because the classification was hardcoded, so any text arriving could be run immediately as a command. Messages are now classified from their content, platform, origin and receiver grouping, and the run-immediately shortcut is taken only when that classification really is ungated. Peer and coordinator messages go through the normal accept-or-hold policy.
[bridge:repl] Ran immediate command without enqueue:
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.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge