Realtime chat messages appear in different order across clients until refresh

Huly version: 0.7.426 self-hosted

Two users send messages alternately:

User A: A001
User B: b001
User A: A002
User B: b002
User A: A003
User B: b003
User A: A004
User B: b004

Client 1 displays:
A001, b001, A002, b002, A003, b003, A004, b004

Client 2 displays:
A001, b001, A002, b002, A003, b003, b004, A004

After refreshing, both clients show the same final order.

Server time is synchronized:
System clock synchronized: yes
NTP service: active

Docker containers share the host clock.

Additional environment information:

- Browser: Chrome 150.0.7871.187
- The two clients are on different local networks, but in the same time zone.
- Huly is accessed through a Lucky reverse proxy.
- The issue occurs in both Chat and Issue Activity.
- The issue has not yet been tested using a normal Chrome window and an Incognito window on the same computer.

Start by reproducing the ordering difference in Chat and Issue Activity with two clients, comparing live updates with the order after refresh. Check whether both clients receive the same events in different sequences; done means newly sent messages retain the same order across clients without requiring a refresh.

Written by the indexing model from the issue text.