moq-native: enable WebSocket keep-alive on the client path

[kixelated]

What

Wire qmux::KeepAlive::default() (5s ping / 30s deadline) into the WebSocket client connect builder in rs/moq-native/src/websocket.rs:

let session = qmux::Client::new()
    .with_protocols(alpns)
    .with_connector(connector)
    .with_keep_alive(qmux::KeepAlive::default()) // 5s ping / 30s deadline — parity with QUIC
    .connect(url.as_str())
    .await

Why

Previously the client WebSocket had no keep-alive, so a half-dead connection (network drop, NAT timeout, dead peer) would hang indefinitely — session.closed() never resolved, the reconnect loop never fired, and recovery required a process restart.

With keep-alive wired up, a half-dead WebSocket misses pings, hits the 30s deadline, the transport closes, session.closed() resolves, and the existing reconnect machinery re-establishes the session automatically. This brings the WebSocket client to parity with the QUIC path's liveness behavior.

The machinery and sensible defaults (KeepAlive::default() = 5s/30s, per qmux 0.0.7) already existed and the server accept path already used them — they just weren't wired up on the client side.

Testing

• cargo check -p moq-native passes.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0d591fd7-b2f6-47e7-8482-54d425c8e70c

📥 Commits

Reviewing files that changed from the base of the PR and between ff03db4 and 9967451.

📒 Files selected for processing (1)

• rs/moq-native/src/websocket.rs

---

Walkthrough

The PR adds an explicit keep-alive configuration to the WebSocket fallback connection in qmux::Client. The change applies .with_keep_alive(qmux::KeepAlive::default()) during builder setup to align the WebSocket path's ping/deadline behavior with the QUIC connection path. No public API changes or other connection setup modifications are made.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: enabling WebSocket keep-alive on the client path in moq-native.
Description check	✅ Passed	The description is directly related to the changeset, providing clear context about what was changed, why it was needed, and how it works.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch websocket-keepalive

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}