Bug: Message ordering broken when client clock is out of sync with server

[kiddlu]

Description

When the client's local clock differs significantly from the server's clock, message ordering in the web UI becomes completely broken. User messages appear after assistant messages, causing the UI to appear stuck in a "thinking" state because the user message is suppressed as being "older" than existing assistant messages.

Plugins

No response

OpenCode version

1.2.15

Steps to reproduce

Set client computer clock to a time significantly different from server (e.g., 2+ hours behind)
Open web UI at http://server:port
Send a message
Observe that the message appears at the wrong position in the timeline

Screenshot and/or share link

No response

Operating System

Debian 13

Terminal

No response

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Clock skew between client and server breaks prompt loop and message rendering #14236: Clock skew between client and server breaks prompt loop and message rendering (same root cause: client/server clock divergence causing message rendering issues)
• Web UI: client-generated message IDs cause infinite processing loop when client/server clocks diverge #11863: Web UI: client-generated message IDs cause infinite processing loop when client/server clocks diverge (same root cause: clock divergence causing web UI message ordering/processing issues)

If your issue is distinct from these, please clarify how it differs. Otherwise, consider adding your details to the existing issues.