The editor bridge pauses writing until a queued conversation reset actually lands.
What's wrong with this entry?
When a conversation reset is still queued and undelivered, the bridge now stops writing messages and stops forwarding queued events until it lands, instead of writing into a conversation that is about to be cleared. If the process shuts down with a reset still undelivered, that is logged with an undelivered_at_teardown outcome and bridge state is torn down.
undelivered_at_teardown
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