deps: bump moq-noq stack to 2.0.2

[kixelated]

Bumps moq-noq-proto, moq-noq-udp, moq-noq, and web-transport-moq from 2.0.1 to 2.0.2, the same way #4699 did for 2.0.1. This puts the max datagram size fix (moq-dev/noq#28) on main, matching what release gets in 1.3.4.

• Cargo.toml: the moq-noq-proto and web-transport-moq pins go to 2.0.2. moq-noq and moq-noq-udp aren't direct workspace deps; they follow through the lockfile.
• Cargo.lock: only these four crates change.
• Deletes quest/m0/noq-2.0.2.md and its entry in quest/m0/README.md.

Public API and wire impact

None. This is a patch-level dependency bump.

Testing

just check: clippy and lint pass. Every test outside moq-uring passes. The moq-uring tests fail locally because they can't create an io_uring: Cannot allocate memory, since io_uring memory counts against RLIMIT_MEMLOCK (8 MiB here), and that limit is shared by every process of the user while several agents are running. This comes from the environment, not the bump; CI should run them normally.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5)

[kixelated]

Quest outcome: done. Only the pins and lockfile change, and there are no open decisions. Local just check passes except moq-uring, whose tests can't get io_uring memory under this host's shared RLIMIT_MEMLOCK while parallel agents run. CI is the real gate for those. Left as a draft for review.

(Written by Claude Opus 5.5)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2203b68b-02fc-4ba5-86a7-69b0a628b21f

📥 Commits

Reviewing files that changed from the base of the PR and between 6dd2930 and 3efe724.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• Cargo.toml
• quest/m0/README.md
• quest/m0/noq-2.0.2.md

💤 Files with no reviewable changes (2)

• quest/m0/README.md
• quest/m0/noq-2.0.2.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

---

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 3efe7

No actionable merge-blocking issue remains in the dependency update or removal of its completed planning notes.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: updating the moq-noq dependency stack to version 2.0.2.
Description check		The description accurately explains the dependency updates, lockfile changes, removed planning note, testing results, and expected environment limitation.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

✨ Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[kixelated]

Merging. Summary: pins moq-noq-proto and web-transport-moq to 2.0.2 (moq-noq and moq-noq-udp follow in the lockfile), bringing the max datagram size fix (moq-dev/noq#28) to main to match release 1.3.4, and deletes the completed quest. No public API or wire impact. CI is green on 3efe724, including the moq-uring tests that could not run locally. CodeRabbit reviewed that head with no actionable findings. No decisions or follow-ups are outstanding.

(Written by Claude Opus 5.5)