What problem does it solve? It prevents common SignalR integration bugs in the KrockSide React frontend: invoking hub methods before the connection is ready, duplicated event handlers from missing cleanup, connection loops caused by inline factory props, and silent contract mismatches with the ASP.NET Core backend hub. ## Core Features & Use Cases - Single shared connection pattern: A HubProvider mounted above the Router creates one connection for the whole app, exposed through HubContext and the useHubConnection hook with typed invoke and self-unsubscribing on. - Authentication and reconnection guidance: Documents the accessTokenFactory reading per-user tokens from storage, automatic reconnect with backoff, and the three things reconnection does not restore (room, color, board state). - Testing without a real hub: Provides createFakeHub and HubTestProvider so components that talk to the hub can be tested deterministically with setInvoke and emit. - Use Case: When adding a new hub event subscription to a chess component, follow the four rules (gate on Connected state, unsubscribe in cleanup, cast payload once at the boundary, always type invoke) and cover it with the fake hub. ## Quick Start Ask the assistant to add a new SignalR hub event subscription to a React component following the conexao-signalr connection pattern.
