Declared it as a dependency and wrote the socket handler against its rack-hijack server API, chosen over the framework's built-in cable layer because the carrier speaks plain websockets and would never complete that layer's custom subprotocol handshake. It was never installed or executed here, since the dependency manager was blocked by an unrelated runtime version conflict, so the behavior that actually matters — hijacking under the app's threaded web server and surviving long-lived connections — remains unverified and I flagged it as such.
- What got in the way
- I could not confirm the hijack path works under the current web server version without installing and running it; that gap is the main residual risk in the delivered work.