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

quest/m0/README.md

@@ -50,11 +50,6 @@ quest, since nothing here waits on it. The [A/V clock](/quest/m1/av-clock.md)
 moved to m1 in the 2026-09-30 audit: it waits on the whole jitter line and is
 a published `@moq/watch` break.
 
-Session caps: since #4820 a peer past a per-session cap loses the session, and
-cluster links get the same 10,000-subscription default. The
-[relay session limits](/quest/m0/relay-session-limits.md) quest gates the next
-release (decided 2026-10-08), so a large mesh link can't flap on the cap.
-
 ## Required
 
 - [Held group wakes](/quest/m0/held-group-wakes.md) - a group held across a route switch is woken when its successor's first timestamp or abort makes it stale, not at the next unrelated append
@@ -65,7 +60,6 @@ release (decided 2026-10-08), so a large mesh link can't flap on the cap.
 - [End of Track Location](/quest/m0/ietf-end-of-track-location.md) - a relay forwards END_OF_TRACK at its upstream's Location, on the last group's stream, instead of re-sending it at the next group's object 0
 - [End of Group status](/quest/m0/ietf-end-of-group-status.md) - an End of Group status on a stream whose header already marks the group's end is accepted, so imquic's last object per group arrives
 - [Subgroup at object 0](/quest/m0/ietf-first-object-zero.md) - a draft-18 subgroup with FIRST_OBJECT clear that starts at object 0 is read whole
-- [Relay session limits](/quest/m0/relay-session-limits.md) - moq-relay sets per-session request limits, tighter for clients than peers, and the bindings name a refused request
 - [Prefix route fronts](/quest/m0/prefix-route-fronts.md) - a prefix route cannot be made to mint one front per requested path
 - [TRACK stream demand](/quest/m0/track-stream-demand.md) - a lite-05+ subscribe shows the publisher one `used` edge, not a flap between TRACK and SUBSCRIBE
 - [Idle fronts](/quest/m0/idle-fronts.md) - a front nobody has read for the linger ends with its per-path state, so a standing claim stops accumulating fronts and sources

quest/m1/README.md

@@ -89,6 +89,7 @@ blocks. The quests that gated m0 lines moved under them.
 - [JS IETF datagrams](/quest/m1/js-ietf-datagram.md) - `@moq/net` sends and receives datagram groups over moq-transport, like Rust
 - [JavaScript FETCH](/quest/m1/js-fetch.md) - browser publishers answer IETF FETCH through the JS ranges request surface
 - [JS request window](/quest/m1/js-request-window.md) - @moq/net grants MAX_REQUEST_ID as requests close, so a peer never stalls after ~21k requests
+- [Relay session limits](/quest/m1/relay-session-limits.md) - moq-relay sets per-session request limits, tighter for clients than peers, and the bindings name a refused request
 - [Churn with held subscriptions](/quest/m1/session-churn-held.md) - opening and closing a request costs the same with 1 or 1,024 held subscriptions
 - [Wide varint tests](/quest/m1/varint-test-gaps.md) - wide sequences and both varint forms are tested where they differ
 - [Export linger](/quest/m1/export-ts-linger.md) - `moq export ts --linger` fails on an export error while the broadcast is live, and lingers once it closes or is replaced

quest/m0/relay-session-limits.md → quest/m1/relay-session-limits.md

@@ -15,10 +15,10 @@ get loose limits. The relay knows
 which sessions are peers, so it picks the limit per session. Propose the flag
 and TOML names in the PR.
 
-This gates the next release (decided 2026-10-08). Past a cap the session
-closes with TOO_MANY_REQUESTS, so until cluster peers get higher caps (or
-none), a link carrying more than 10,000 subscriptions closes and flaps on
-reconnect.
+Past a cap the session closes with TOO_MANY_REQUESTS, so until cluster peers
+get higher caps (or none), a link carrying more than 10,000 subscriptions
+closes and flaps on reconnect. This does not gate a release (decided
+2026-10-08).
 
 Add the error kind to `rs/moq-ffi` and every wrapper per the Cross-Package
 Sync table.