[Web] WebRTC connection lifecycle — missing timeout, aggressive cleanup, orphaned connections

[Flegma]

Summary

WebRTC data channel handling has lifecycle issues causing hangs and resource leaks.

Findings

• Webrtc.ts — promise for data channel has no timeout. If channel never opens, promise hangs indefinitely.
• Webrtc.ts — dataChannel.onclose calls cleanupPeer() immediately while peer may still be referenced.
• MatchmakingStore — 5-second timeout resolves outer promise but WebRTC connection continues. No cleanup on timeout.

Impact

Latency checks hang forever on failed connections. Orphaned WebRTC connections accumulate.

Suggested Fix

Add timeout to data channel open promise. Delay peer cleanup for graceful shutdown. Clean up WebRTC on timeout.

---

Related Issues (WebSocket/Networking Pattern)

• [API] Harden match events gateway authentication and message validation #371 — [API] Harden match events gateway
• [Web] WebSocket reconnection needs exponential backoff with jitter #387 — [Web] WebSocket exponential backoff
• [Web] WebRTC connection lifecycle — missing timeout, aggressive cleanup, orphaned connections #388 — [Web] WebRTC connection lifecycle
• [Connector] RCON connection corruption, Redis silent failure, missing send timeout #408 — [Connector] RCON connection & Redis reliability