Message order is not delivery order. Messages can take different paths, and two students can reconnect at different moments, so arrival order belongs to the network. For an accurate shared-workspace roster, assign order on the authoritative server, expose sequence numbers so clients can detect gaps, and refetch current state after a gap or reconnect. Do not rebuild presence by replaying whatever happened to arrive.
TL;DR: test presence as a state-reconciliation problem, not a perfectly ordered stream. The five checks are monotonic authority, deliberate reordering, a visible gap, reconnect recovery, and duplicate tolerance. Pass only if every client converges on the server's roster without displaying a stale event as newer truth.
In plain terms, Infrai is one candidate for the notification-and-presence leg when a team also needs other backend modules behind the same REST contract and key.…