Queued messages and control frames now replay in the order they were made after a reconnect.
What's wrong with this entry?
While the remote bridge is holding traffic during a flush or reconnect, transcript messages and control frames used to sit in two separate queues and drain one after the other. Every queued item now carries a sequence number and the drain interleaves them, preserving original order.
- The two drain log lines were merged into one.
- No flag; unconditional in this build.
queued message(s) and
Strings lifted out of the shipped bundle, so the claim above can be checked against them.