quest: delete stats-linger now that its release backport merged

quest/m0/README.md

@@ -24,9 +24,6 @@ The branch flip is done except its #4605 backport to `release`; the
 Cloudflare switch waits on the maintainer as a condition quest.
 The DoS hardening from an external review on 2026-09-29, verified against `main`, stays in m0
 as security work. Its quests describe fixes, not exploits.
-[Stats linger](/quest/m0/stats-linger.md) joined m0 on 2026-10-05 as a
-standalone quest, not a release gate: moq.pro's m0 waits on a `release`
-commit carrying it, so it lands on main and is backported.
 
 Routing: the wildcard line is prefix-only on the wire; its resolve and demand
 work is done on the line branch and waits to land. Serving the relay's
@@ -53,7 +50,6 @@ a published `@moq/watch` break.
 - [Request caps](/quest/m0/request-caps.md) - lite message sizes, IETF request IDs, and per-session announces and subscriptions are bounded
 - [qmux credit](/quest/m0/qmux-credit.md) - qmux returns connection credit for dropped and stopped streams and delivers its close frame, on both lines
 - [Shared fronts](/quest/m0/shared-fronts.md) - viewer sessions share a front, so fronts scale with peers, not viewers, and viewer churn no longer leaks fronts
-- [Stats linger](/quest/m0/stats-linger.md) - landed on `main`; the `release` backport remains, so moq.pro's grouped stats broadcasts stop re-announcing on viewer churn
 - [Wildcard](/quest/m0/wildcard/README.md) - a relay resolves subscriptions against advertised prefixes, a service claims the prefix it could serve and refuses the rest instead of enumerating broadcasts, and the browser player treats a covering claim as availability
 - [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - every first-party publisher that can restart mints a fresh `@<uuidv7>` epoch, viewers follow the newest live one, and bare names still resolve on every version
 - [Audio jitter target](/quest/m0/audio-jitter-target/README.md) - the audio playout target is a measured estimate of arrival timing in both languages, not a round-trip guess

quest/m0/broadcast-epoch/stats-aggregate-bound.md

@@ -45,4 +45,3 @@ Public API: none expected beyond a possible grace-window knob on
 
 - [Stats epochs](/quest/m0/broadcast-epoch/stats-epoch.md) - every restarted node gets a new name, so retired entries churn faster
 - [Binary delta stats](/quest/m2/stats-delta.md) - also sweeps the aggregate over node count
-- [Stats linger](/quest/m0/stats-linger.md) - a group's node broadcast outlives a short gap instead of churning an aggregate entry

quest/m0/broadcast-epoch/stats-split.md

@@ -88,7 +88,6 @@ across nodes.
 
 ## Related
 
-- [Stats linger](/quest/m0/stats-linger.md) - the idle-group window these totals continue across
 - [Bounded stats aggregate](/quest/m0/broadcast-epoch/stats-aggregate-bound.md) - retired
   nodes fold into a bounded total; per-epoch totals feed it
 - [Media stats](/quest/m1/stats/README.md) - publisher and viewer media stats

quest/m1/bench-buckets.md

@@ -39,7 +39,7 @@ so the bench emits mergeable buckets. Approved as recommended.
   taken. Update `rs/moq-bench/README.md`.
 
 Lands on main, then is backported to `release` as an additive cherry-pick
-PR, like [Stats linger](/quest/m0/stats-linger.md), since moq.pro's load
+PR, like [#4882](https://github.com/moq-dev/moq/pull/4882), since moq.pro's load
 harness tracks `release` (decided 2026-10-05). The backport carries #3126's
 delta along if `release` does not have it yet.