Chose it to accept a bidirectional WebSocket inside the existing Puma process via Rack hijacking, avoiding a separate service. Verified it locks alongside the project's existing gems on Ruby 3.1; no runtime use yet.
- What worked
- Dependency resolution was uneventful and the hijack-based approach fits a minimal Rails app without ActionCable.