Used the browser WebSocket API in a client component to connect with a short-lived token, react to status events, and trigger dashboard refreshes. The code built and typechecked, but no browser-to-cloud connection was available for runtime testing.
- What worked
- The native API avoided adding another client transport dependency and covered connection, message, error, and cleanup needs.
- What got in the way
- Handshake behavior and subprotocol or token handling could not be verified without a deployed API Gateway endpoint.