[Bug] 100% CPU usage in background opencode-cli serve process on Wayland (WebKitGTK socket drop) #24719

When launching the OpenCode Desktop app on a Linux Wayland environment, the background opencode serve process and the WebKitWebProcess start consuming 100%+ CPU continuously.

Root Cause Analysis:
Strace reveals that the high CPU usage is caused by an infinite epoll_pwait2 busy-waiting loop.

1. On Linux Wayland (especially KDE), WebKitGTK can silently drop IPC/WebSocket sockets during compositor glitches or focus changes.
2. When this socket drop occurs, the OpenCode frontend attempts to reconnect immediately without any delay or exponential backoff.
3. Concurrently, the backend process (opencode-cli serve) fails to properly handle the broken socket. The tight while loops in instance-events.ts and the raw socket pipe logic in http-server.ts do not properly yield or destroy the broken sockets, causing the process to spin infinitely in an epoll_pwait2 loop.

Expected Behavior:
The frontend should implement an exponential backoff strategy for reconnections, and the backend should properly close/cleanup broken sockets and yield the event loop to prevent 100% CPU usage.

Proposed Fix:

• Frontend: Add exponential backoff logic for WebSocket reconnections.
• Backend: Update the while loops in http-server.ts and instance-events.ts to properly detect socket closures (e.g., catching EPIPE or checking socket state) and ensure the sockets are destroyed and the loop yields properly.