超时的 WebSocket 会话对客户端来说看起来就像是崩溃 (没有发送真正的 WS 关闭帧)

Bug description:

When a WebSocket/CDP session hits the configured TIMEOUT, browserless does try to tell the client - onWebsocketTimeout in src/router.ts calls writeResponse(socket, 408, 'Request has timed out') - but by the time a session is active, that socket is no longer a plain HTTP connection. It's already being piped bidirectionally to the real Chrome instance by http-proxy inside ChromiumCDP.proxyWebSocket (src/browsers/browsers.cdp.ts), so it's mid-stream WebSocket frame data at that point, not raw HTTP.