quest: move relay session limits back to m1, no release gate

[kixelated]

Problem

While merging #4820, the merge agent took the maintainer's "merge" as option 1 of an open cluster-cap question (comment 6050708340). As a result, it moved quest/m1/relay-session-limits.md to m0 and marked it as gating the next release. The maintainer never made that call.

Approach

• Move the quest back to quest/m1/relay-session-limits.md and restore its m1 README entry.
• Drop the m0 README entry and the "Session caps ... gates the next release" paragraph.
• Keep the factual flap risk in the quest's Plan: past 10,000 subscriptions, a cluster link closes and flaps on reconnect. Record that the quest does not gate a release.

✅ Revert to m1, no gate (chosen)

• Keep the m0 release gate
• Move to m0, no release gate

Impact

• Public API: none. Wire: none. Quest files only; quest check passes.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 10 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: b6de20b5-fffc-479c-9ade-cfe74b2b72a4

📥 Commits

Reviewing files that changed from the base of the PR and between 2717724 and 8ca39e5.

📒 Files selected for processing (3)

• quest/m0/README.md
• quest/m1/README.md
• quest/m1/relay-session-limits.md

• Autopilot · 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]

Grok review of 8ca39e5 (quest/docs only)

Accurate revert of the m0 move that landed with #4820. I checked it against main:

• No other quest or doc on main links /quest/m0/relay-session-limits.md. The only references were the m0 README's Session caps paragraph and Required entry, and this PR removes both, so no link breaks after the rename.
• The facts kept in the quest's Plan match the code: moq_net::session::Limits::default() is 100,000 announces and 10,000 subscriptions (rs/moq-net/src/session.rs:665-670), and moq-relay doesn't set Limits anywhere yet (nothing in cluster.rs, session.rs or config.rs), so cluster links get the same default and can hit TooManyRequests.
• The m0 Goal and Plan text that's left don't mention session caps, and the broadcast-epoch release gate paragraph is unchanged, so the README doesn't contradict itself.

Non-blocking:

• With the gate gone, the next release ships feat(net)!: bound peer-declared lengths and per-session requests #4820's caps while peer links still use the 10,000-subscription default. A mesh link past that closes and flaps on reconnect. That's your call to make, but it may be worth a line in the moq-relay release notes so operators running large clusters know about it until this quest lands.

No blocking issues. CI (Check, Quest, Test) was still queued when I reviewed.

Verdict: MERGE once CI is green.

This is an automated review, not the maintainer's decision
(Written by Grok)

[kixelated]

Automated review by review (OpenAI)

Reviewed full commit 8ca39e5dabc6a274564800f022be1300bc6b846c against 2717724cec9e608681fb1a0ad6a1d7fce70d266c.

No actionable findings. The three-file change consistently moves the quest and its README entry back to m1, removes the m0 release gate, and retains the existing cluster-cap flap warning. This is a minimal implementation of the stated planning decision; public API, wire behavior, and runtime limits are unchanged.

Verification: inspected the complete diff, changed documents, quest tree, and linked #4820 discussion through GitHub. No local commands or tests run; Check, Test, and Quest are queued. Rechecked that the PR is open and non-draft, the head is unchanged, and there are no existing reviews or inline findings.

[kixelated]

Merge summary for 8ca39e5d:

• Moves quest/m0/relay-session-limits.md back to quest/m1/, restores its m1 README entry, and drops the m0 entry plus the "Session caps ... gates the next release" paragraph. The quest's Plan keeps the cluster-link flap risk past 10,000 subscriptions and states it does not gate a release.
• Decision: revert to m1 with no release gate, chosen by the maintainer.
• Main moved by two commits (fix(net): reset a subscription that cannot encode a later group #4984, fix(net): honor SUBSCRIBE_NAMESPACE options and fill draft-16+ streams #5032); the head merges onto it cleanly and quest check passes on the merged tree.
• Review: OpenAI review of 8ca39e5d had no actionable findings.

Enabling auto-merge pinned to 8ca39e5dabc6a274564800f022be1300bc6b846c.

(Written by Claude Opus 5.5)