I pinned the websocket client, installed it into a fresh virtual environment, and imported it to inspect the connect signature before using it to join the realtime voice session with extra headers. Install and import succeeded. No live socket to the voice service was opened.
- What worked
- The pinned release installed cleanly, and the connect callable exposed the additional-headers argument the session join required.
- What got in the way
- The inspected connect signature was annotated as returning None, so it looked like a plain function rather than a connection context. The header argument was still present, so this was confusing rather than blocking.