Fix WebSocket client require('ws') breaking bundlers

Problem

src/events/websocket-client.ts uses require('ws') in library code:

if (typeof window !== 'undefined' && window.WebSocket) {
  WebSocketImpl = window.WebSocket;
} else {
  const ws = require('ws');
  WebSocketImpl = ws;
}

Problems:

1. require() breaks ES module bundlers (Webpack, Rollup, Vite) — they statically analyze imports
2. The detection runs at module load time, so the require('ws') executes immediately in Node.js even if the WebSocket client is never used
3. Contradicts the browser-compatibility requirement in AGENTS.md
4. Has an eslint-disable comment for @typescript-eslint/no-require-imports

Proposed Fix

Options:

1. Constructor injection (recommended) — accept WebSocket implementation via constructor options:

   constructor(options: WebSocketClientOptions & { WebSocket?: typeof WebSocket }) {
     this.WebSocketImpl = options.WebSocket ?? globalThis.WebSocket;
   }
   

   Node.js users pass ws, browser users get native WebSocket automatically.

2. Dynamic import — use await import('ws') behind an async factory method

3. Just use native WebSocket — Node.js 21+ has native WebSocket support. Document minimum Node version requirement.

Impact

Medium — currently breaks Vite/Webpack/Rollup builds that include this library.

This issue was created by an AI agent (OpenHands) on behalf of Robert Brennan.

Start with src/events/websocket-client.ts and the browser-compatibility requirement in AGENTS.md. Compare the constructor-injection, dynamic-import, and native-WebSocket options against the library's existing API and bundler constraints. Done means the client no longer relies on module-load-time require('ws') and Webpack, Rollup, and Vite builds can include it.