fe2b7d8e8a
poll_loop now: 1. Tries WebSocket connection to /v1/ws/<fingerprint> 2. On success: receives messages in real-time (instant push) 3. On disconnect: reconnects after 3 seconds 4. On WS failure: falls back to HTTP polling every 2 seconds Refactored message processing into shared functions: - process_incoming() handles raw bytes - process_wire_message() handles deserialized WireMessage - Used by both WS and HTTP paths Both CLI TUI and web client now use WebSocket: - No more HTTP polling spam in server logs - Messages arrive instantly on both clients - HTTP poll kept as fallback for scripts/mules Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>