[BUG] Messages out-of-order after ban/unban fix

[Cod-e-Codes]

Summary
After the frozen-history fix (b9407f6), some clients display messages in the wrong order.

Steps to reproduce

1. Connect Client A and B.
2. Send messages M1–M3.
3. Ban Client A.
4. Send messages M4–M6 from B.
5. Unban Client A and reconnect.
6. Send more messages (M7–M8) and check ordering.

Observed

• Messages sometimes appear out-of-order.
• Persists after client restarts.
• Affects some clients intermittently.

Expected
All messages should appear in chronological order.

Suspected causes

• Server query may lack deterministic ORDER BY.
• Client merge logic may misplace messages.
• Timestamp collisions or sequence-ID mismatch.

Next steps

• Ensure server returns messages in a consistent order.
• Client should sort messages by sequence ID before rendering.
• Add a test for ordering after ban/unban + reconnect.

[Cod-e-Codes]

Fixed in 4ab352b (and accompanying client/server updates).

The root cause of messages displaying out-of-order was inconsistent ordering between the server and client. Changes made:

• Added consistent sorting on the server (GetRecentMessages / GetMessagesAfter) to guarantee messages are returned in chronological order.
• Updated the client (renderMessages and Update) to sort messages by timestamp when rendering and after receiving new messages.
• Verified builds and tested the client — messages now display in correct order across sessions without needing a new server instance.

This closes the out-of-order messages bug. If any inconsistencies remain, please open a new issue with reproduction steps.