websocket-handler-decomposition

To refactor a WebSocket handler, split it into a thin orchestrator that delegates to a ConnectionManager for keepalive and locking, and a MessageDispatcher for routing and replay, preserving the HandleAsync signature to avoid breaking callers.

Separating concerns in WebSocket handlers involves extracting transport and session logic into a ConnectionManager, and routing with replay persistence into a MessageDispatcher, while explicitly preserving public endpoint mappings and the HandleAsync signature.

Extract a ConnectionManager and MessageDispatcher by making the top-level handler a thin orchestrator, moving reconnect throttling and keepalive to the manager, and shifting inbound message routing and replay persistence to the dispatcher.

Refactoring WebSocket handlers requires updating dependency injection registrations and adjusting tests to explicitly wire the new ConnectionManager and MessageDispatcher components into the application pipeline.

You should split a WebSocket handler when it accumulates transport lifecycle, session locking, message routing, and replay persistence, and you need to improve maintainability while preserving endpoint and method contracts.

Preserving the HandleAsync signature during a WebSocket refactor limits breaking changes to public contracts but requires internal delegation to new components, necessitating dependency injection updates and test adjustments to wire the new structure.