diff --git a/bench/README.md b/bench/README.md index 122cf36296c..8d01957feaa 100644 --- a/bench/README.md +++ b/bench/README.md @@ -203,7 +203,7 @@ also run during timing. Every timed round reads and checks all payload bytes, returns lease credit, and fills each stream again. Throughput counts delivered payload once. Nightly's supplemental Rust benchmark leg records the series and keeps the memory output with its raw results. The broader MoQ session transport -and version sweep remains in [its quest](/quest/m2/bench-transport-sweep.md). +and version sweep remains in [its quest](/quest/m4/bench-transport-sweep.md). Compare one multi-threaded Tokio runtime with the same number of independent Tokio/epoll and io\_uring workers: diff --git a/doc/concept/socket.md b/doc/concept/socket.md index 47533add9ad..f9f609c8692 100644 --- a/doc/concept/socket.md +++ b/doc/concept/socket.md @@ -137,7 +137,7 @@ every hop, so a slow reader slows the writer, as TCP backpressure does, and nothing is lost. A writer that doesn't wait sheds the front of its half, and a reader that falls behind it fails with an eviction error instead of skipping data. Pacing reaches across native QUIC and qmux hops; see -[unbounded groups](https://github.com/moq-dev/moq/tree/main/quest/m1/unbounded-groups) +[unbounded groups](https://github.com/moq-dev/moq/tree/main/quest/m2/unbounded-groups) for what remains, such as browsers, which read without pacing. Use `tcp` for a byte stream or a log of records that must all arrive in order, diff --git a/infra/README.md b/infra/README.md index 0451046f908..b5c9e6ea4eb 100644 --- a/infra/README.md +++ b/infra/README.md @@ -42,7 +42,7 @@ which can update an existing worker but not create one or change its route. So the first deploy, and any change to the custom domain, runs by hand under a maintainer's `wrangler login`. Whether Editor alone passes wrangler's custom-domain check on every deploy is unproven until the first `release` -run; [the deploy quest](../quest/m2/release/moq-sh-deploy.md) tracks it. +run; [the deploy quest](../quest/m3/release/moq-sh-deploy.md) tracks it. ## Write credentials diff --git a/quest/README.md b/quest/README.md index e5e084f463b..93025fa18e8 100644 --- a/quest/README.md +++ b/quest/README.md @@ -7,23 +7,42 @@ grouped into milestones ordered by priority. ## Plan -m0 holds urgent fixes and release-line maintenance. m1 is everything that -lands before the next cut of `main` into `release`, breaking or not: -clustering stability first, the in-tree QUIC stack, and planned public API and -format breaks with their correctness and validation. -m2 holds independently shippable capabilities and optimizations, plus the -publication and adoption steps that follow m1. m3 holds external conditions -and speculative work. A milestone is a priority horizon; m0 maintenance does -not make unrelated infrastructure a gate for the main-to-release cut. - -Milestones shift up after each major release (decided 2026-10-19): m0 is the -current release line, m1 the next major, m2 the one after, and m3 stays the -deferred bucket. The [release cut](/quest/m2/release/cut.md) recurs and -performs the shift. The hygiene audits at the end of each milestone recur -once per major release: each run adds its successor to the end of the next -milestone. - -The [release execution](/quest/m2/release/README.md) starts after m1 is ready. +m0 holds urgent work of any type: release-line maintenance, broken CI and +Nightly, and any fix that cannot wait for its milestone, breaking or not. +m1 holds this cycle's additive work: improvements and fixes that need no +semver-breaking release, so each ships with the next cut or as a `release` +patch when backported. m2 is the next breaking release: every change that +would need one if it landed right after the cut, plus the +[cut gate](/quest/m2/cut-gate/README.md). The cut waits on m2 alone. m3 and m4 +are later work split by priority: m3 holds what a named consumer waits on, +release execution, and bug fixes in shipped code; m4 holds tests, tooling, +benchmarks, optimizations, and features nobody waits on yet. m5 holds work +gated on the outside world, or speculative work with no named consumer. + +A change is breaking when a published consumer or a deployed peer must adapt +to it: the public Rust, JS, or bindings API, a frozen wire version, the hang +catalog JSON, a stored or exported container format, or CLI flags, config +keys, and environment variables. The test is whether it would need a breaking +release if it landed right after the cut, so a change to lite-07-wip or to a +`main`-only API the cut would publish counts. A non-urgent fix that breaks +joins m2; when a non-breaking fix exists, the fix joins m1 and the break m2. +An epic joins the milestone its outcome needs, children included. + +Decided 2026-11-05 (maintainer, milestone re-cut): milestones split by kind of +change for the current cycle and by priority after it. This replaces m1 as +"everything before the cut, breaking or not" (2026-10-20). Grouping by kind +could bury urgent breaking work behind additive work, so urgency still wins: +urgent work of either kind joins m0. + +Milestones shift after each cut (decided 2026-10-19, rule replaced +2026-11-05). The [release cut](/quest/m3/release/cut.md) recurs and performs +the shift: remaining release-execution quests move to m0, m3's quests split +by kind into m1 and m2, m4's move to m3, m4 starts empty, and m5 stays the +deferred bucket. The cut PR also re-creates the cut gate in m2. The hygiene +audits recur once per major release in m3, behind the cut, so the shift +brings each into m1. + +The [release execution](/quest/m3/release/README.md) starts once m2 is done. It publishes artifacts before downstream adoption and rollout can complete. Critical fixes continue to reach the existing release through backports. @@ -35,7 +54,9 @@ planning PR's review is the check. ## Required -- [m0: immediate priorities](/quest/m0/README.md) - urgent correctness fixes and maintenance of the current release -- [m1: next wave](/quest/m1/README.md) - everything before the next release cut, breaking or not, with its required correctness and validation -- [m2: later work](/quest/m2/README.md) - byte streams and mesh libraries first, then release execution, deferred features, optimization, and design studies -- [m3: deferred](/quest/m3/README.md) - gated on the outside world (hardware, a partner, a consumer, a provider's offer, or an upstream release), or speculative with no named consumer +- [m0: immediate priorities](/quest/m0/README.md) - urgent work of any kind, and maintenance of the current release +- [m1: additive work](/quest/m1/README.md) - this cycle's improvements and fixes that need no breaking release; each ships with the next cut or as a backported patch +- [m2: the next breaking release](/quest/m2/README.md) - every change that would need a breaking release if it landed after the cut, plus the cut gate; the cut waits on m2 alone +- [m3: later work, higher priority](/quest/m3/README.md) - byte streams and mesh libraries first, release execution, what a named consumer needs, and bug fixes in shipped code +- [m4: later work, lower priority](/quest/m4/README.md) - tests, tooling, benchmarks, optimizations, and features nobody waits on yet +- [m5: deferred](/quest/m5/README.md) - gated on the outside world (hardware, a partner, a consumer, a provider's offer, or an upstream release), or speculative with no named consumer diff --git a/quest/m0/ci/mbx-r2-verify.md b/quest/m0/ci/mbx-r2-verify.md index 9ad7fc95641..457d80806ca 100644 --- a/quest/m0/ci/mbx-r2-verify.md +++ b/quest/m0/ci/mbx-r2-verify.md @@ -25,7 +25,7 @@ nightly.yml --branch main --event schedule`), never a dispatch on a branch. ## Plan Decided 2026-11-05 (maintainer, /quest-audit): ✅ the release pull request -check moved to [m2](/quest/m2/mbx-r2-release-cache.md) behind the cut, since +check moved to [m3](/quest/m3/mbx-r2-release-cache.md) (m2 before the milestone re-cut) behind the cut, since `release` gets the platform Rust cache only when the cut merges `main` into it; the Nightly checks stay here. Not chosen: moving this whole quest; merging `main` into `release` now, which reverses the 2026-11-04 decision. diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index 7acdbbeddb6..062d391faf1 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -29,7 +29,7 @@ patch cut on `release`, which the maintainer cuts. Dart: pub.dev publishes `moq` only from a `moq-dart-v*` tag, and only `moq-dart-v0.1.0` exists. Pushing `moq-dart-v0.1.1` at `release`'s head publishes 0.1.1 and exercises the unproven path in -[A Dart tag publishes unattended](/quest/m2/release/dart-publish.md). Decided +[A Dart tag publishes unattended](/quest/m3/release/dart-publish.md). Decided 2026-10-30 (maintainer): push it during the combined cut, not before. Decided 2026-11-04 (maintainer, /quest-unblock): ✅ cut the combined patch @@ -43,4 +43,4 @@ Public API: none. Wire: none. ## Related -- [A Dart tag publishes unattended](/quest/m2/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses +- [A Dart tag publishes unattended](/quest/m3/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses diff --git a/quest/m1/README.md b/quest/m1/README.md index 3fc57731bfc..e8bbbfac793 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -1,170 +1,47 @@ -# m1: clustering stability and the next release +# m1: additive work for this cycle ## Goal -Everything that lands before `main` is next cut into `release`: stable -clustered routing and recovery, the switch to moq-quic, the planned public -API and format changes, and the non-breaking fixes and checks queued ahead of -the cut. Complete this milestone before cutting main into release. +Improvements, fixes, and checks that need no semver-breaking release: each +lands on `main` and ships with the next cut, or as a `release` patch when it +is backported. Breaking work for the same cut lives in m2. ## Plan -Decided with the maintainer on 2026-10-15: clustering stability and the -in-tree QUIC stack first. Decided 2026-10-20 (maintainer): m1 is everything -before the cut, not only breaking work, so ready non-breaking quests stay -here instead of moving out; the cut is what ships them. - -- Preserve epoch correctness, routing recovery, outbound federation, and - claim continuity on lite-07. Catalogs, long-lived readers, - and late joiners obey the same identity contract. -- Keep IETF passthrough, the API audit, the broad clock conversion, - archive replay/DVR correctness, and the TS fidelity - expansion in m1. Keep their correctness, interoperability, memory, and - performance evidence with them. -- Defer P2P, watch-worker planning and implementation, AMD Vulkan encode and - Intel VA-API/Vulkan import, and QoS lag and prefix stats to m2 with their - prerequisites. Their possible API breaks do not make them prerequisites of - this cut. Existing playback and A/V clock validation remain here. - Same-epoch importers were dropped (maintainer, 2026-10-19): a redundant - ingest pair runs on distinct epochs. -- Finalized lite-07 is preferred by first-party Rust and JS clients, with - older-version negotiation fallback. Servers accept it by default. Never - reuse a published identifier for an incompatible wire change; deferred - features use the appropriate subsequent wip/version if they need one. -- The next cut makes no new AMD/Intel GPU-input support promise. The later - multi-vendor release needs both hardware proofs before publication. -- Package publication, downstream adoption, and production rollout follow - the cut under [release execution](/quest/m2/release/README.md). - -Existing upgrade and identity guides carry migrations; feature docs change -inline. Keep generic proofs here and deployments and their operational -acceptance with the downstream operator. - -Keep one owner per shared code area and order prerequisites before consumers -(re-ranked in the 2026-10-20 audit: auth before cluster routing, and every -lite-07 prerequisite before those quests). -Decided 2026-10-25 (maintainer): the hand-written `moq-c` ships at this cut -with parity to moq-ffi for every m1 binding feature, so each binding quest -lands its C half there; the generated C line moves after the cut. -The moq-transport passthrough fields remain crate-private: no public moq-net -item exists only for moq-transport (maintainer, 2026-10-23). - -Added 2026-10-16: refresh, a breaking `Demand` change, so it lands before -the cut. - -Added 2026-10-22 (maintainer, from an external API audit): small breaks -that would otherwise force another breaking release (the FFI encoder config, -FromStr, dead items, `SessionClosed`, unprefixed C++), the hang draft's -warmup rule for the shipping dual decoder, the binding migration guide fixes, -and the API-diff tooling. Public routes now wait on cluster routing. - -Added 2026-10-20 (maintainer): the probe target, native probing, and the -native rung disable moved up from the [m2 probe epic](/quest/m2/probe/README.md), -so Rust, FFI, and OBS publishers recover a stopped rendition in this release; -padding and the browser's rung disable stay in m2, with only padding's -lite-07 stream type here. - -Added 2026-10-22 (maintainer, clustering audit): three interim fixes for -announce churn on today's hop-list mesh, shipping with the next cut from -`main` (not backported to `release`), so deployments get relief before the -route layer ships; and stats groups as -tracks, so per-group stats stop costing cluster announces. - -Added 2026-10-22 (maintainer, security audit of the relay, auth, stats, -ACME, and WebRTC): a clean close misreported as a revocation, injectable -metric tiers, an unbudgeted ACME renewal, unbounded mDNS work per WebRTC -offer, and an undocumented stats linger cut. The audit's `server_name` -finding was already fixed by moq-dev/moq#6509. - -Added 2026-10-23 (maintainer, from a linger audit): broadcasts lose their -finished state and retention moves to moq-mux, a break in every binding, so -it lands before the cut. - -Added 2026-10-23 (maintainer, from a moq-quic audit): moq-quic and its drivers -are unreleased, so their API is reshaped before the cut publishes it, and the -audit's receive-memory, priority, and lease bugs rank ahead of that reshape. - -Added 2026-10-23 (maintainer, pre-cut triage): breaks that would otherwise -force another major (`announce="never"`, the unused OBS outputs, binding -durations, and the remaining web-transport-trait adapters) land before the -cut, as do the small hostile-input and container fixes from the 2026-10-22 -security audit, and the stuck-window scan. - -Added 2026-10-24 (maintainer, from a moq-hls audit): import and export -hardening (URL redaction, ranged responses, redirect bases, sequence -arithmetic, DASH init readiness, dot-only names) and ffprobe segment -conformance; the audit's segment-finalization redesign is folded into -Catalog HLS field. - -Added 2026-10-24 (maintainer-requested pre-cut audit of main): remote -crashes and amplification in media and RTMP parsing, lite announce bounds, -JS track terminal causes, browser element teardown, and smaller Rust/JS -divergences, under one epic; its redesign proposals went to m2. - -Decided 2026-10-26 (maintainer): every MoQ crate takes its crypto from -[rind](/quest/m1/rind/README.md), a pure-Rust graviola fork, so the cut ships -no C crypto. This supersedes the same day's move of pure-Rust crypto to m3. -Dropping the `rsa` crate from moq-auth's production graph stays in m1. - -Added 2026-10-25 (maintainer): the studio's -GPU encode and source import quests are in m1 so -moq-video's GPU encode and import API changes, mainly encoders taking a GPU -surface and zero-copy texture import, land before the cut. - -Added 2026-10-27 (maintainer, from an external security audit): relay and -wire boundary fixes, importer streaming, moq-c handle wrap, browser input -checks, and CI tool pins, under one epic; its credential leaks went to m0. - -Added 2026-11-01 (maintainer): datagram tracks, so lite-07 freezes with -datagrams as their own track kind instead of single-frame groups. - -Added 2026-11-01 (maintainer, follow-up planning): byte-stream ladders, so -the binding API for `lower` breaks before the cut, `moq export` ending -with its broadcast, and a relay answering a SUBSCRIBE on a fetched copy. - -Added 2026-10-27 (maintainer, from an external release-to-main audit): the -bindings' silent `max_delay` default change and the upgrade notes that -contradict the code. Its other findings already had owners or contradicted -settled decisions (archives break in place; OBS video-only output stays -removed). - -Added 2026-11-01 (maintainer, follow-ups from the 2026-11-01 /quest-afk run): -the shared pacer's overshoot under 2 Mbit/s with the BBR3 retune it needs, -since BBR3 is the default controller the cut ships; a truncated MKV that -left its tracks open; and, under release performance, a bisect of the relay's -per-frame CPU growth since #5926. - -Added 2026-11-04 (maintainer): the relay reports the native sessions its -drain deadline force-closes while still open, apart from those only finishing -their end report, so an embedder's drain alert pages on real cuts. - -Decided 2026-11-05 (maintainer, /quest-audit): blockers rank above the -quests that require them. - -- ✅ Move the blockers up: Drop set and Subscribe ranges rank just above - Address groups by timestamp, and the API audit just above Cluster routing. -- Not chosen: moving the dependents down; leaving the order as it was. +Decided 2026-11-05 (maintainer, milestone re-cut): m1 is the additive half +of what was "everything before the cut" (2026-10-20). A quest stays here when +it would need no breaking release if it landed right after the cut; the rest +moved to [m2](/quest/m2/README.md), and m1's earlier decision log moved with +them, since it is the cut's. The cut no longer waits on m1: what lands before +it ships with it, and the rest ships at a later cut or as a `release` patch. + +Placements decided in the re-cut: read-backfill (a JS fix that matches Rust), +buffered-ascending (lite-07 already carries the order field), webrtc-vendor +(internal, though it requires the m2 rename), and the crates.io trusted +publisher and OIDC quests (setup after the cut's first publishes) are +additive. [video-vaapi](/quest/m1/video-vaapi.md) moved up from later work +because a downstream iGPU transcode trial needs it now. + +Held here by open claims: a quest's branch is its path, so a claimed quest +cannot move until its PR merges, and an epic moves with its children. These +breaking epics and quests stay in m1 for now and are listed in m2's +`Required`, so the cut still waits on them: api-audit, datagram-tracks, drop-set, rind, session-policy, and +stream-credit. The [re-cut follow-up](/quest/m2/recut-held.md) +moves what remains of them once their claims merge. release-perf, held for +the same reason, gates the cut through the +[cut gate](/quest/m2/cut-gate/README.md). ## Required - [Drop set](/quest/m1/drop-set.md) - each cursor judges missing groups against its own budget, so a narrow reader drops promptly and a widening re-offers groups already reported dropped on lite-07 -- [Subscribe ranges](/quest/m1/subscribe-ranges/README.md) - a lite-07 SUBSCRIBE asks for past and live ranges with absolute or relative ends, in either order, and replaces FETCH for multi-group reads (single-group FETCH stays); merged ranges never starve a subscriber; relays fill misses by range, including over moq-transport -- [Address groups by timestamp](/quest/m1/time-addressing/README.md) - group start timestamps replace sequence numbers in the moq-net API and lite-07 wire, while old subscribers, old publishers, and published JS clients keep working -- [Pre-cut audit findings](/quest/m1/cut-audit/README.md) - fix the crashes, hostile-input costs, and correctness bugs the 2026-10-24 audit of main found -- [Vendored code has every upstream fix it needs](/quest/m1/vendor-sync/README.md) - quinn, libv4l-rs, nvidia-video-codec-sdk, rust-media-libs, cros-codecs, and UniFFI generator fixes are ported or planned, once per release cycle - [Media fuzz findings](/quest/m1/fuzz-findings/README.md) - the nightly media fuzz targets run clean: mp4-atom, MKV block, TS step, SPS overflow, and catalog encoder bugs they found are fixed - [A smaller, safer API than release](/quest/m1/api-audit/README.md) - every surface added since release has a consumer or is gone, overlapping operations are collapsed, names mirror across Rust, JS, and the bindings, and every break says how to migrate -- [Cluster routing](/quest/m1/cluster-routing/README.md) - prove shared routing contracts, implement per-origin routes, and connect outbound local clusters - [Routing guide](/quest/m1/routing-guide.md) - concepts and practical outbound federation setup -- [moq-c at parity](/quest/m1/c/README.md) - the hand-written `moq-c` ships at the cut with every m1 binding feature moq-ffi gains -- [A job's exact route continues its claim's readers](/quest/m1/announce-takeover.md) - a job's route inherits its claim's instance, replacing the ANNOUNCE_TAKEOVER predecessor design - [A reader on a failed copy continues on the held re-offer](/quest/m1/copy-recover.md) - a live reader keeps a group whose copy fails by continuing on the same track's re-offer at the same frame - [Group errors are cached by kind](/quest/m1/group-error-cache.md) - permanent group errors bind every reader, retryable ones are kept only for a bounded time, and a live SUBSCRIBE_DROP or FETCH answered `Old` no longer caches it for good -- [A group a subscriber gives up on is always reported](/quest/m1/group-drops.md) - the wire names every abandoned group and the drop signal is public, so readers count losses instead of stalling - [The overcommitted receive-window cells run again](/quest/m1/receive-windows-evicted.md) - `benchmark_receive_windows` measures its 256-stream and 4 MiB-frame cells again, reporting delivered frames and evictions instead of stalling - [Datagram tracks](/quest/m1/datagram-tracks/README.md) - a track is datagrams or streams; datagram tracks have their own request and sequence, no ranges, no cache, and map to object ID 0 on moq-transport - [Stream credit by priority](/quest/m1/stream-credit/README.md) - every stream opens through one priority entry point, and a higher-priority group takes over or resets a lower one when credit runs out -- [Finalize moq-lite-07](/quest/m1/lite07-finalize.md) - when the maintainer cuts it, lite-07 negotiates as `moq-lite-07` and the next release ships it - [Sockets](/quest/m1/socket/README.md) - a generic dial/accept `Socket` in moq-net, Rust, JS, and Python, with tracks as streams; moq-boy and CARLA move onto it - [Audio jitter target](/quest/m1/audio-jitter-target/README.md) - the playout target is default in both languages; time-stretched browser playback without steady-state underruns and a native trace replay remain - [Container reads drop backfill](/quest/m1/read-backfill.md) - the JS container consumer drops groups below its read cursor like Rust @@ -178,8 +55,11 @@ quests that require them. - [Calibrate the paired nightly benchmarks](/quest/m1/bench-ci.md) - `rust-bench` fits its hour and gets A/A runs, and separate builds of unchanged code stop measuring as a slowdown, so every paired regression alert can be trusted - [moq-json's table/deltas bench measures the same work every iteration](/quest/m1/bench-json-deltas.md) - the `table/deltas/1%` cases stop flipping between snapshot and delta timings, so their trend history is usable - [Publish moq-bench to crates.io](/quest/m1/bench-publish.md) - `cargo install moq-bench` installs one binary, with the host sampler as `moq-bench host`, first as 0.1.0 -- [Unbounded groups](/quest/m1/unbounded-groups/README.md) - groups and frames lose their size caps; a group keeps a 32 MB tail, and readers behind it replay through paced flights or refresh - [Session policy lives in moq-net](/quest/m1/session-policy/README.md) - accept and connect deadlines, admission, window widening and reconnect live once in moq-net; moq-tokio and moq-relay's io_uring path call them -- [Rename moq-rtc to moq-webrtc](/quest/m1/webrtc-rename.md) - one published `moq-webrtc` crate holds the gateway, the ICE driver, and the data-channel transport - [Vendor and trim the WebRTC stack](/quest/m1/webrtc-vendor.md) - str0m, dimpl, `is`, and sctp-proto live in moq-webrtc with unused code removed, so moq-rtc can take rind - [MoQ on rind](/quest/m1/rind/README.md) - every MoQ crate takes its crypto from rind, a pure-Rust graviola fork, so no build compiles C crypto +- [VAAPI encode and decode](/quest/m1/video-vaapi.md) - H.265 encode and decode, pre-generated bindings, and pooled resize surfaces, including the moq-dev/vaapi release that carries them + +## Related + +- [A busy js/net serve yields](https://github.com/moq-dev/moq/pull/5289) - js/net's serve loop leaves the browser its event loop under a fast publisher, if it does not already diff --git a/quest/m1/api-audit/README.md b/quest/m1/api-audit/README.md index 5bc24033622..ba3863d96f1 100644 --- a/quest/m1/api-audit/README.md +++ b/quest/m1/api-audit/README.md @@ -9,7 +9,7 @@ Names mirror across Rust, JS, and the bindings. Every break says how to migrate. Non-goals: redesigning independently scoped surfaces -([subscribe ranges](/quest/m1/subscribe-ranges/README.md), +([subscribe ranges](/quest/m2/subscribe-ranges/README.md), [archives](/doc/concept/archives.md), [compressed tracks](/doc/concept/compression.md), and `Sync`'s per-track clock handles), and inherited debt that a later quest @@ -32,7 +32,7 @@ Rules every child follows: - Removal beats addition. A surface with no consumer in the repository, moq.pro, or moq.dev goes private or away. A consumer planned in a quest - counts only when that quest is in m1. + counts only when that quest is in m1 or m2. - Inherited debt is fixed here only when it is cheap or sits on a surface this release breaks anyway. Otherwise it joins the later quest that reshapes it (the ordered track reader joins rust2's diff --git a/quest/m1/api-audit/route/README.md b/quest/m1/api-audit/route/README.md index d070f5b8149..8b01bb75f62 100644 --- a/quest/m1/api-audit/route/README.md +++ b/quest/m1/api-audit/route/README.md @@ -17,8 +17,8 @@ kinds. Rust, JS, moq-ffi, moq-c and the wrappers mirror it. Non-goals: the route layer's wire messages and federation -([Routes and announces](/quest/m1/cluster-routing/routes/README.md)), lite-07 -takeover ([announce takeover](/quest/m1/announce-takeover.md)), and any +([Routes and announces](/quest/m2/cluster-routing/routes/README.md)), lite-07 +takeover ([announce takeover](/quest/m2/announce-takeover.md)), and any moq-transport instance ([moq-transport carries no epoch](https://github.com/moq-dev/moq/pull/7239)). ## Plan @@ -144,7 +144,7 @@ supersede the epoch-minting, pairing and run-uniqueness answers above: predecessor-ID plan. The predecessor design then landed on main in [moq-dev/moq#6994](https://github.com/moq-dev/moq/pull/6994). On - 2026-10-31 the maintainer kept identity: [announce takeover](/quest/m1/announce-takeover.md) + 2026-10-31 the maintainer kept identity: [announce takeover](/quest/m2/announce-takeover.md) now also removes that work, so only one continuity rule remains. Third round, 2026-11-01, answering @@ -171,5 +171,5 @@ stale, including `doc/concept/identity.md`. ## Related -- [A job's exact route continues its claim's readers](/quest/m1/announce-takeover.md) - a job's route inherits its claim's instance, so lite-07 readers keep the first subscribe -- [Routes and announces](/quest/m1/cluster-routing/routes/README.md) - the wire route layer; instances take over its epochless deletion +- [A job's exact route continues its claim's readers](/quest/m2/announce-takeover.md) - a job's route inherits its claim's instance, so lite-07 readers keep the first subscribe +- [Routes and announces](/quest/m2/cluster-routing/routes/README.md) - the wire route layer; instances take over its epochless deletion diff --git a/quest/m1/audio-jitter-target/watch.md b/quest/m1/audio-jitter-target/watch.md index 729e0e0a2e9..cbf9b8a41bb 100644 --- a/quest/m1/audio-jitter-target/watch.md +++ b/quest/m1/audio-jitter-target/watch.md @@ -178,4 +178,4 @@ latency, Bluetooth included, is part of the lip sync. - [Capped budgets](/quest/m1/audio-jitter-target/capped-budgets.md) - re-measures the AAC browser budgets after the publisher change, no gate on this proof - [Native stretch](/quest/m1/audio-jitter-target/native-stretch.md) - the native time-stretch sharing one NetEq algorithm and its test vectors with this one -- [Watch worker](/quest/m2/watch-worker.md) - moves the worklet this stretch changes +- [Watch worker](/quest/m3/watch-worker.md) - moves the worklet this stretch changes diff --git a/quest/m1/bench-publish.md b/quest/m1/bench-publish.md index 8bd6259e384..3b850e5a941 100644 --- a/quest/m1/bench-publish.md +++ b/quest/m1/bench-publish.md @@ -50,9 +50,9 @@ crate, like CONTRIBUTING's bench-only backport. Otherwise skip it, say so in the PR, and moq-bench publishes at the cut. The first publish goes out by token, so add moq-bench to the -[crates.io trusted publisher](/quest/m2/crates-trusted-publisher.md) +[crates.io trusted publisher](/quest/m3/crates-trusted-publisher.md) `Waiting` list (done in this planning PR). ## Related -- [crates.io trusts the workflow](/quest/m2/crates-trusted-publisher.md) - moq-bench needs a trusted publisher after its first publish +- [crates.io trusts the workflow](/quest/m3/crates-trusted-publisher.md) - moq-bench needs a trusted publisher after its first publish diff --git a/quest/m1/buffered-ascending.md b/quest/m1/buffered-ascending.md index 70cc5eb9a58..38e3a4211cf 100644 --- a/quest/m1/buffered-ascending.md +++ b/quest/m1/buffered-ascending.md @@ -38,7 +38,7 @@ Decided 2026-10-23 by the maintainer: max-delay release rules go. Not chosen: delete the hold outright; keep #6549's rules unchanged. - ✅ The hold stays audio-only. Video's startup hold is the poster quest's. -- ✅ Placed in m1, requiring [Finalize moq-lite-07](/quest/m1/lite07-finalize.md): +- ✅ Placed in m1, requiring [Finalize moq-lite-07](/quest/m2/lite07-finalize.md): lite-06 and earlier serve an ascending request newest-first, so this is a no-op on default sessions until lite-07 negotiates by default. `release` has no `order` field, so it ships in the next minor, not a 0.6.x patch. @@ -77,9 +77,9 @@ keeps waiting on lite-07 for the head-hold simplification. ## Required -- [Finalize moq-lite-07](/quest/m1/lite07-finalize.md) - an ascending request is served newest-first until lite-07 negotiates by default +- [Finalize moq-lite-07](/quest/m2/lite07-finalize.md) - an ascending request is served newest-first until lite-07 negotiates by default ## Related - [Container reads drop backfill](/quest/m1/read-backfill.md) - the JS consumer stops delivering groups below its cursor -- [Subscribe ranges](/quest/m1/subscribe-ranges/README.md) - owns the wire's `Group Order` and the ordered cursor's floor +- [Subscribe ranges](/quest/m2/subscribe-ranges/README.md) - owns the wire's `Group Order` and the ordered cursor's floor diff --git a/quest/m1/datagram-tracks/README.md b/quest/m1/datagram-tracks/README.md index e6da124a255..def636b5d50 100644 --- a/quest/m1/datagram-tracks/README.md +++ b/quest/m1/datagram-tracks/README.md @@ -22,7 +22,7 @@ Decided 2026-11-01 (maintainer, in `/quest-plan`): - **Datagrams are a track-level decision.** ✅ A track is datagrams or streams, never a mix. This reverses the - [subscribe-ranges](/quest/m1/subscribe-ranges/README.md) decision of + [subscribe-ranges](/quest/m2/subscribe-ranges/README.md) decision of 2026-10-20 that any single-frame group may go as a datagram, including a copy of a streamed one. With no mixing, the stream/datagram dedup rule, the ordering of a datagram among its group's streams, NOT_FETCHABLE, and every @@ -39,7 +39,7 @@ Decided 2026-11-01 (maintainer, in `/quest-plan`): the group sequence space. On moq-transport it maps to a group ID with object ID 0. - This exempts datagrams from - [lite-07 by start](/quest/m1/time-addressing/lite07.md): they keep a + [lite-07 by start](/quest/m2/time-addressing/lite07.md): they keep a sequence, while stream tracks address groups by start. - The timestamp stays, as it does for every frame. - **Discovery.** ✅ The application knows which kind a track is, through its @@ -93,7 +93,7 @@ Decided 2026-11-01 (maintainer, in `/quest-plan`): - Reason: a stream handler need not answer a name it doesn't serve, and the bindings' rejection carries only an application error. - **Version.** ✅ lite-07, before it is finalized. - [Finalize moq-lite-07](/quest/m1/lite07-finalize.md) requires this epic. + [Finalize moq-lite-07](/quest/m2/lite07-finalize.md) requires this epic. lite-01..06 keep today's group datagrams. Decided by the Rust child ([moq-dev/moq#7752](https://github.com/moq-dev/moq/pull/7752)), @@ -109,7 +109,7 @@ not the maintainer, so open to revisiting: while compression would cost every datagram an Inflated Size and a decoder. - **Timestamp on a `Timescale` 0 track.** The datagram carries none, and its Sequence stands in for its time. Why: it mirrors the - [model](/quest/m1/time-addressing/model.md)'s rule that a scale-less frame's + [model](/quest/m2/time-addressing/model.md)'s rule that a scale-less frame's timestamp is its group's key, since a datagram's address is its sequence. Until that model lands, Rust's datagram writes take `Option` like frame writes do (`None` on an untimed track), and the model quest converts @@ -125,7 +125,7 @@ datagram track on lite-07, direct and through a relay. ## Related -- [Subscribe ranges](/quest/m1/subscribe-ranges/README.md) - ranges no longer cover datagrams -- [Address groups by timestamp](/quest/m1/time-addressing/README.md) - stream tracks address by start; datagram tracks keep a sequence -- [Wrapper traits over moq-net](/quest/m2/net-wrap/README.md) - the traits mirror the separate datagram types -- [moq-lite session tails count drops](/quest/m2/lite-tail-drop-count.md) - datagram holes matter only on lite-05/06 +- [Subscribe ranges](/quest/m2/subscribe-ranges/README.md) - ranges no longer cover datagrams +- [Address groups by timestamp](/quest/m2/time-addressing/README.md) - stream tracks address by start; datagram tracks keep a sequence +- [Wrapper traits over moq-net](/quest/m5/net-wrap/README.md) - the traits mirror the separate datagram types +- [moq-lite session tails count drops](/quest/m3/lite-tail-drop-count.md) - datagram holes matter only on lite-05/06 diff --git a/quest/m1/drop-set.md b/quest/m1/drop-set.md index ce08026076d..c250763b2dc 100644 --- a/quest/m1/drop-set.md +++ b/quest/m1/drop-set.md @@ -17,7 +17,7 @@ narrower budget is served after a widening, as a cold relay would. Decided 2026-10-27 (maintainer): this runs after the range count cost work, which finished in [moq-dev/moq#7542](https://github.com/moq-dev/moq/pull/7542), since both edit `given_up` in `rs/moq-net/src/model/track/miss.rs`, and before -[Rust groups by start](/quest/m1/time-addressing/model.md), which requires it +[Rust groups by start](/quest/m2/time-addressing/model.md), which requires it because runs keyed by group sequence convert mechanically to starts. Decided by the maintainer on 2026-10-19, splitting this from the widened @@ -190,7 +190,7 @@ A cursor judges an unknown missing sequence (never a stale run its record still holds as reported, which only a widening settles) as it would a group never received: locally against its own budget (`TrackState::drifted`), and otherwise as a cache miss, which the relay fills upstream by range -([Subscribe ranges](/quest/m1/subscribe-ranges/README.md)), so no reader +([Subscribe ranges](/quest/m2/subscribe-ranges/README.md)), so no reader waits indefinitely on forgotten state. Extend `track_subscriber_churn` in `rs/moq-net/benches/track.rs` with a fragmented set up to pool capacity, swept over subscriber count, shared runs, runs per cursor record, and run @@ -318,4 +318,4 @@ start can carry the budget it was resolved under. ## Related -- [Subscribe ranges](/quest/m1/subscribe-ranges/README.md) - fills the cache miss an evicted run leaves +- [Subscribe ranges](/quest/m2/subscribe-ranges/README.md) - fills the cache miss an evicted run leaves diff --git a/quest/m1/group-error-cache.md b/quest/m1/group-error-cache.md index 08b7284d10c..691f801a927 100644 --- a/quest/m1/group-error-cache.md +++ b/quest/m1/group-error-cache.md @@ -83,4 +83,4 @@ mirror, if a caller outside moq-net needs it; otherwise none. Wire: none. ## Related -- [A group a subscriber gives up on is always reported](/quest/m1/group-drops.md) - reports what a subscriber gives up; this decides how long the track remembers it +- [A group a subscriber gives up on is always reported](/quest/m2/group-drops.md) - reports what a subscriber gives up; this decides how long the track remembers it diff --git a/quest/m1/moq-e2ee-remove.md b/quest/m1/moq-e2ee-remove.md index 1a8a05ceba0..28dd27a4c90 100644 --- a/quest/m1/moq-e2ee-remove.md +++ b/quest/m1/moq-e2ee-remove.md @@ -10,7 +10,7 @@ moq-crypto, is on crates.io. ## Plan Decided 2026-11-05 (maintainer, /quest-audit): ✅ retire the stub before -[Rust releases publish through OIDC](/quest/m2/release-rs-oidc.md), so the +[Rust releases publish through OIDC](/quest/m3/release-rs-oidc.md), so the crate never needs a trusted publisher. Published 2026-11-05 (maintainer, /quest-unblock, by an agent at the diff --git a/quest/m1/read-backfill.md b/quest/m1/read-backfill.md index 7a090cd1472..cbd22136c40 100644 --- a/quest/m1/read-backfill.md +++ b/quest/m1/read-backfill.md @@ -27,7 +27,7 @@ delivers a group that arrives below the cursor as a late backfill; Rust after the live edge; a cursor set from the first arrival would lose valid startup media (`consumer.outoforder.test.ts` covers that order). The floor is instead the lowest group of the subscription's requested ranges - ([Subscribe ranges](/quest/m1/subscribe-ranges/README.md)): given for an + ([Subscribe ranges](/quest/m2/subscribe-ranges/README.md)): given for an absolute start, and for a relative start the start the publisher resolved for this request. Every sequence in range arrives or is named by SUBSCRIBE_DROP, so the read never waits on a group that won't come. @@ -55,7 +55,7 @@ delivers a group that arrives below the cursor as a late backfill; Rust Decided 2026-10-27 (maintainer): this waits only on the resolved start in SUBSCRIBE_OK and JS ranges, not the whole -[Subscribe ranges](/quest/m1/subscribe-ranges/README.md) epic. Both have +[Subscribe ranges](/quest/m2/subscribe-ranges/README.md) epic. Both have landed: the resolved start, and JS ranges in [moq-dev/moq#7696](https://github.com/moq-dev/moq/pull/7696). A range that a SUBSCRIBE_UPDATE adds gets its start from SUBSCRIBE_STARTED diff --git a/quest/m1/receive-windows-evicted.md b/quest/m1/receive-windows-evicted.md index 95702b3a105..366ead9ee98 100644 --- a/quest/m1/receive-windows-evicted.md +++ b/quest/m1/receive-windows-evicted.md @@ -8,7 +8,7 @@ overcommitted cells again, and Nightly's `Rust benchmark tests` job (`gh nightly rust-test`) still passes. Those cells are 256 streams, 4 MiB frames, and 4 MiB frames with a following stream window. Until then, the benchmark skips them and prints each one with -`quest/m1/group-drops.md` as the reason. +`quest/m2/group-drops.md` as the reason. Every cell keeps the workload it offers. A cell whose incomplete units fit the connection window fails on any eviction. A cell that @@ -20,7 +20,7 @@ alongside throughput and latency, instead of failing. Moved to m1 2026-11-04 with the maintainer, after [moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) landed the fitting cells: what remains waits on -[group-drops](/quest/m1/group-drops.md), an m1 quest, and with the +[group-drops](/quest/m2/group-drops.md), an m2 quest, and with the overcommitted cells skipped the benchmark no longer fails Nightly, so this no longer holds the m0 [Nightly passes on main](/quest/m0/nightly/README.md) epic open. It replaces @@ -37,7 +37,7 @@ Overload policy, decided 2026-11-04 (maintainer): Silent loss, decided 2026-11-04 (maintainer): -- ✅ Fix it at the source in `quest/m1/group-drops.md`, planned in +- ✅ Fix it at the source in `quest/m2/group-drops.md`, planned in [moq-dev/moq#7890](https://github.com/moq-dev/moq/pull/7890). There, the wire always names an abandoned group, and `track::Subscriber`'s drop signal becomes public. @@ -84,7 +84,7 @@ What remains: `Cell::fits` partition in `benchmark_receive_windows`), and run the full sweep through `quest gate`. - Retain the stream/frame/window axes and the actual offered workload - for [Receive pool](/quest/m2/receive-pool.md). + for [Receive pool](/quest/m5/receive-pool.md). - Repro: `just rs test -p moq-tokio --test integration --release -E 'test(benchmark_receive_windows)' --run-ignored only --success-output immediate`. @@ -99,4 +99,4 @@ Public API: none. Wire: none. ## Required -- [A group a subscriber gives up on is always reported](/quest/m1/group-drops.md) - the public drop signal the reader needs to return a dropped group's permit +- [A group a subscriber gives up on is always reported](/quest/m2/group-drops.md) - the public drop signal the reader needs to return a dropped group's permit diff --git a/quest/m1/release-perf/README.md b/quest/m1/release-perf/README.md index 9268aa4ec94..c5536c5c5e5 100644 --- a/quest/m1/release-perf/README.md +++ b/quest/m1/release-perf/README.md @@ -10,7 +10,7 @@ and the reason is written here. This epic's own work: once its children have landed, re-pair the relay `fanout` workload against `release` and confirm main's relay CPU is no higher in every round. The sparse rows are accepted (2026-10-30). The browser frame path -needs no repeat; the [performance audit](/quest/m2/audit-perf.md) now pairs +needs no repeat; the [performance audit](/quest/m3/audit-perf.md) now pairs every later cut with `release`. ## Plan @@ -181,7 +181,7 @@ Accepted, flat per operation: - e2ee `protect` is 1.5x release on grouped frames and 1.21x on datagrams. The crypto is unchanged; the rest is the per-group model cost accepted above. Both branches expand the AES-GCM key on every frame, about a quarter of - `protect`, which the [performance audit](/quest/m2/audit-perf.md) owns. + `protect`, which the [performance audit](/quest/m3/audit-perf.md) owns. - gst `moqsink/eos` is +12% instructions per event, from [#5512](https://github.com/moq-dev/moq/pull/5512) and the gstreamer-rs 0.25 bump in [#6169](https://github.com/moq-dev/moq/pull/6169). @@ -194,7 +194,7 @@ Accepted, flat per operation: frame) and the IETF `/fetch` delivery rows also reappear unchanged. - The TS export still grows with track count (1.50x at `1x1` to 2.24x at `16x64`). The T-STD schedule scans and sorts every queued unit per PCR slot, - which the [performance audit](/quest/m2/audit-perf.md) owns. + which the [performance audit](/quest/m3/audit-perf.md) owns. Noise: `frame_recv/upfront/size=262144/streams=64` is 3 to 4x in wall time at 0.96x instructions. Its 1.6M page faults (against 192k) are glibc returning @@ -220,7 +220,7 @@ Decided 2026-10-25 (maintainer), in the cut; [moq-dev/moq#6921](https://github.com/moq-dev/moq/pull/6921) flattened it. - The TS schedule's growth is left to the - [performance audit](/quest/m2/audit-perf.md); it does not block the cut. + [performance audit](/quest/m3/audit-perf.md); it does not block the cut. - Now that the sparse fix has landed, re-run the relay fanout pairing on a quiet host, recording `/proc/loadavg`, with `BENCH_ARTIFACTS= just bench origin/release` (it also re-checks @@ -356,5 +356,5 @@ live read is accepted, per delivered group through the session (see the ## Related -- [Performance audit](/quest/m2/audit-perf.md) - compares nightly to nightly; this epic compares main to release +- [Performance audit](/quest/m3/audit-perf.md) - compares nightly to nightly; this epic compares main to release - [Calibrate the paired nightly benchmarks](/quest/m1/bench-ci.md) - noise floor of the paired nightly-to-nightly comparison on one runner diff --git a/quest/m1/rind/README.md b/quest/m1/rind/README.md index 10f64ab8fe5..9b5b6b0e7a3 100644 --- a/quest/m1/rind/README.md +++ b/quest/m1/rind/README.md @@ -36,8 +36,8 @@ instead, so every crate drops C, not just the relay. and aws-lc-rs do, so their aarch64 builds keep running, and every area that runs in moq-cli or moq-relay switches only once that rind release ships. This keeps - [cli-packaging](/quest/m2/cli-packaging.md)'s Pi 4 V4L2 publishing and - [embedded video](/quest/m3/video-embedded.md) on those boards. + [cli-packaging](/quest/m3/cli-packaging.md)'s Pi 4 V4L2 publishing and + [embedded video](/quest/m5/video-embedded.md) on those boards. - x86_64 CPUs without AVX2, BMI2, ADX, or AES-NI get the same treatment (maintainer, 2026-11-01): rind picks slower paths for them at startup, and the same areas wait on that release too. @@ -48,7 +48,7 @@ instead, so every crate drops C, not just the relay. uses, so most areas switch on rind 0.1.2 (published 2026-11-01), which runs on CPUs without the crypto extensions (e2ee, which no binary links, switched on 0.1.0). Relay ACME, the one area that waited on `rind-instant-acme`, is - removed for now instead (maintainer, 2026-11-03), and returns on rind in m3. + removed for now instead (maintainer, 2026-11-03), and returns on rind in m5. aws-lc-rs stays in the workspace until the last area lands, which is when this epic removes it. - Split per area, each landing once rind covers it. Docs a change makes stale diff --git a/quest/m1/rind/rtc.md b/quest/m1/rind/rtc.md index fc4c19d0670..3e694b8b923 100644 --- a/quest/m1/rind/rtc.md +++ b/quest/m1/rind/rtc.md @@ -16,7 +16,7 @@ and reqwest switches to its no-provider feature. The existing browser interop tests prove the switch. Decided 2026-10-30 (maintainer): the stack is vendored into moq-webrtc -([epic](/quest/m2/webrtc/README.md)) with DTLS 1.2 only, so this quest +([epic](/quest/m3/webrtc/README.md)) with DTLS 1.2 only, so this quest changes the vendored crypto provider directly and offers no DTLS 1.3. Decided 2026-10-31 (maintainer): the vendored crates are private modules, so diff --git a/quest/m1/routing-guide.md b/quest/m1/routing-guide.md index 6fb1d57211d..ecadd8aa997 100644 --- a/quest/m1/routing-guide.md +++ b/quest/m1/routing-guide.md @@ -23,10 +23,10 @@ link-cost policy outside the basic setup. Use generic public examples and validate CLI/config examples against the implemented help. Cross-link `doc/bin/relay/cluster.md` and identity guidance -without duplicating reference material. Route health adds its section in m2. +without duplicating reference material. Route health adds its section in m5. Public API/wire: documentation only, reflecting completed implementations. ## Required -- [Outbound federation](/quest/m1/cluster-routing/federation.md) - tested operator configuration +- [Outbound federation](/quest/m2/cluster-routing/federation.md) - tested operator configuration diff --git a/quest/m1/session-policy/README.md b/quest/m1/session-policy/README.md index 3a8b93ac898..05865ae6f61 100644 --- a/quest/m1/session-policy/README.md +++ b/quest/m1/session-policy/README.md @@ -20,7 +20,7 @@ maintainer asked what that means for io_uring and how much of moq-tokio belongs in moq-net, and decided: - ✅ **Move the policy first**, then give moq-tokio thin handoffs; the - [WebRTC rename](/quest/m1/webrtc-rename.md) waits on + [WebRTC rename](/quest/m2/webrtc-rename.md) waits on [moq-tokio becomes a thin shell](/quest/m1/session-policy/tokio-handoff.md) (#7804 closed unmerged). Not chosen: a moq-tokio handoff now with the move later; moq-webrtc calling @@ -57,7 +57,7 @@ Research (2026-11-04, `origin/main` at e6be13d5f8): - Widening on admit needs a transport hook: moq-net's `transport::poll` session exposes only `receive_window()`, while tokio QUIC, qmux and uring's `web::Session` all have `set_limits`. Add a trait method whose default - reports unsupported, the same move [QUIC deadline](/quest/m2/quic-deadline.md) + reports unsupported, the same move [QUIC deadline](/quest/m5/quic-deadline.md) plans for per-stream deadlines. - moq-net stays poll-first and spawns nothing ([libraries spawn nothing](https://github.com/moq-dev/moq/pull/6849)): diff --git a/quest/m1/session-policy/connect.md b/quest/m1/session-policy/connect.md index aab876ced54..716a18d992e 100644 --- a/quest/m1/session-policy/connect.md +++ b/quest/m1/session-policy/connect.md @@ -24,7 +24,7 @@ reconnect moves too, not just the deadline. `connection.rs` tests to the moq-net machines on kio's simulator, so the same timings are asserted without tokio. - This also gives a future io_uring client - ([uring-cluster-dial](/quest/m3/uring-cluster-dial.md)) the policy to reuse + ([uring-cluster-dial](/quest/m5/uring-cluster-dial.md)) the policy to reuse rather than copy. Public API: breaking in moq-net's `Client` and new reconnect types; moq-tokio's diff --git a/quest/m1/session-policy/tokio-handoff.md b/quest/m1/session-policy/tokio-handoff.md index 493082e47c8..3a9310bb17a 100644 --- a/quest/m1/session-policy/tokio-handoff.md +++ b/quest/m1/session-policy/tokio-handoff.md @@ -8,14 +8,14 @@ handoffs for transports established elsewhere: `accept_with(transport, link)` on the listener and `connect_with(transport)` on the client, which run the moq-net accept or connect policy over an already-connected session and return the usual request or session. moq-tokio's own `webrtc` module goes through -them, so the [WebRTC rename](/quest/m1/webrtc-rename.md) moves it into +them, so the [WebRTC rename](/quest/m2/webrtc-rename.md) moves it into moq-webrtc without reaching into moq-tokio's internals. ## Plan Part of [Session policy lives in moq-net](/quest/m1/session-policy/README.md); see it for the decisions and research. This is what the -[WebRTC rename](/quest/m1/webrtc-rename.md) waits on +[WebRTC rename](/quest/m2/webrtc-rename.md) waits on ([moq-dev/moq#7804](https://github.com/moq-dev/moq/pull/7804), which first asked, closed unmerged): the maintainer decided on 2026-11-04 to move the policy first, so the handoff is a few lines over diff --git a/quest/m1/session-policy/uring.md b/quest/m1/session-policy/uring.md index 2963e8b48cc..1a67830d0ff 100644 --- a/quest/m1/session-policy/uring.md +++ b/quest/m1/session-policy/uring.md @@ -25,7 +25,7 @@ see it for the decisions and research. runs on the worker handle, with admission hopping to the shared runtime through `Lifecycle::shared`, so one `Connection::run` serves every runtime. Use one listen-config mapping at all three sites. -- Do this before [the io_uring packaging work](/quest/m2/relay-io-uring-package.md) +- Do this before [the io_uring packaging work](/quest/m3/relay-io-uring-package.md) publishes the duplicated path. - The relay's existing drain, admission and handshake-deadline tests must pass on both runtimes. @@ -38,4 +38,4 @@ Public API: none. Wire: none. ## Related -- [io_uring relay package](/quest/m2/relay-io-uring-package.md) - ships the path this unifies +- [io_uring relay package](/quest/m3/relay-io-uring-package.md) - ships the path this unifies diff --git a/quest/m1/socket/README.md b/quest/m1/socket/README.md index b35051f3fdf..7fb41850115 100644 --- a/quest/m1/socket/README.md +++ b/quest/m1/socket/README.md @@ -5,16 +5,16 @@ `moq-net` gains a generic dial/accept primitive. An `Endpoint` announces one hidden broadcast, dials other endpoints, and accepts their dials, and each connection is a session between the two ends: a reliable, ordered byte pipe -each way (`tcp`), or a track of messages each way (`track`). moq-boy, CARLA, [byte streams](/quest/m2/stream/README.md), and the -mesh [Endpoint](/quest/m2/mesh/endpoint.md) all build on it instead of each +each way (`tcp`), or a track of messages each way (`track`). moq-boy, CARLA, [byte streams](/quest/m3/stream/README.md), and the +mesh [Endpoint](/quest/m3/mesh/endpoint.md) all build on it instead of each hand-rolling the announce, watch, and request loop. Rust, JS, and Python (through moq-ffi) expose the same surface and interoperate. Non-goals: a wire change to moq-lite (a socket is a path and track convention over existing announce and subscribe streams); session caps, leases, or idle timeouts, which stay application logic (boy's 60 s idle, CARLA's one-driver -lease and 1 s watchdog); signing and encryption, which the m2 -[mesh](/quest/m2/mesh/README.md) owns by making endpoint ids public keys. +lease and 1 s watchdog); signing and encryption, which the m3 +[mesh](/quest/m3/mesh/README.md) owns by making endpoint ids public keys. ## Plan @@ -81,10 +81,10 @@ pipe below; the second round above adds the acceptor to the session name: 16 MiB past its reader on each hop, and a reader that falls off the tail fails with `Evicted` rather than skipping data. Where pacing doesn't reach yet, that `Evicted` is the failure mode, never silent loss: browsers and JS - read unpaced ([JS fastest-reader pacing](/quest/m2/js-fastest-reader.md)), + read unpaced ([JS fastest-reader pacing](/quest/m4/js-fastest-reader.md)), and a session past its paused-credit cap (about two paused group streams at the client defaults) reads and sheds instead of pausing. That remaining - pacing work stays in the [unbounded groups](/quest/m1/unbounded-groups/README.md) + pacing work stays in the [unbounded groups](/quest/m2/unbounded-groups/README.md) epic, which this depends on for lossless `tcp` in those cases. Implementation choices in @@ -180,7 +180,7 @@ replacement arc), still standing: Later, not built now: a multiplexed `quic` protocol, `quic///` on the same endpoint with no new announcement, which brings back several groups or streams per session; and signed or encrypted sessions with ids as public -keys, in the m2 [mesh](/quest/m2/mesh/README.md). +keys, in the m3 [mesh](/quest/m3/mesh/README.md). This epic owns removing the hand-rolled loops: after the ports, no announce-watch-request pairing remains in `rs/moq-boy`, `js/moq-boy`, or @@ -194,5 +194,5 @@ announce-watch-request pairing remains in `rs/moq-boy`, `js/moq-boy`, or ## Related -- [Byte streams](/quest/m2/stream/README.md) - TCP over sockets, one session per connection -- [Endpoint API](/quest/m2/mesh/endpoint.md) - the mesh's `connect`/`accept`, a socket endpoint plus signing +- [Byte streams](/quest/m3/stream/README.md) - TCP over sockets, one session per connection +- [Endpoint API](/quest/m3/mesh/endpoint.md) - the mesh's `connect`/`accept`, a socket endpoint plus signing diff --git a/quest/m1/socket/js.md b/quest/m1/socket/js.md index 47b5454ddfc..16671a7e8b2 100644 --- a/quest/m1/socket/js.md +++ b/quest/m1/socket/js.md @@ -21,7 +21,7 @@ Both carry `peer` and `session`, and no message methods of their own. Session tracks are `///` in both endpoints, served only on request so no listing names them; an unknown or unaccepted protocol is reset as unsupported. JS reads without fastest-reader pacing until -[JS fastest-reader pacing](/quest/m2/js-fastest-reader.md), so a JS `tcp` +[JS fastest-reader pacing](/quest/m4/js-fastest-reader.md), so a JS `tcp` reader that falls a group tail behind fails with an eviction error; say so in the docs. As in Rust, dials and accepts fail as unsupported while the endpoint's connection is moq-lite before 07, which never carries its hidden diff --git a/quest/m1/ts-reliability/README.md b/quest/m1/ts-reliability/README.md index 3557b6a4e99..49d55df2f2d 100644 --- a/quest/m1/ts-reliability/README.md +++ b/quest/m1/ts-reliability/README.md @@ -139,4 +139,4 @@ catalog linger (#5305). ## Related -- [MSFTS mapping](/quest/m3/msfts-convergence.md) - document the exact equivalence and differences between the carriage modes +- [MSFTS mapping](/quest/m5/msfts-convergence.md) - document the exact equivalence and differences between the carriage modes diff --git a/quest/m2/video-vaapi.md b/quest/m1/video-vaapi.md similarity index 98% rename from quest/m2/video-vaapi.md rename to quest/m1/video-vaapi.md index 9420f1d99d0..e501d00777f 100644 --- a/quest/m2/video-vaapi.md +++ b/quest/m1/video-vaapi.md @@ -62,4 +62,4 @@ already falls back cleanly, since `Encoder::new` returns `Err` and ## Related -- [VA-API encodes an external Vulkan image](/quest/m2/vaapi-vulkan-import.md) - explicit-sync DMA-BUF input and render-node selection by device, H.264 only +- [VA-API encodes an external Vulkan image](/quest/m3/vaapi-vulkan-import.md) - explicit-sync DMA-BUF input and render-node selection by device, H.264 only diff --git a/quest/m1/webgpu-safari.md b/quest/m1/webgpu-safari.md index 124df479ea0..81f421b2812 100644 --- a/quest/m1/webgpu-safari.md +++ b/quest/m1/webgpu-safari.md @@ -87,4 +87,4 @@ Public API: possibly a new `out.error` name. Wire: none. ## Related -- [WebGPU HDR](/quest/m2/webgpu-hdr.md) - builds on the same renderer +- [WebGPU HDR](/quest/m5/webgpu-hdr.md) - builds on the same renderer diff --git a/quest/m1/webrtc-vendor.md b/quest/m1/webrtc-vendor.md index 2908aea189a..7f4abd186d5 100644 --- a/quest/m1/webrtc-vendor.md +++ b/quest/m1/webrtc-vendor.md @@ -6,18 +6,18 @@ moq-webrtc builds str0m, dimpl, `is`, and sctp-proto from private in-tree module ## Plan -Decided 2026-10-30 with the maintainer (planning interview); see the [epic](/quest/m2/webrtc/README.md) for what goes and why. +Decided 2026-10-30 with the maintainer (planning interview); see the [epic](/quest/m3/webrtc/README.md) for what goes and why. -Milestone: ✅ m1 (moved from m2, maintainer, 2026-11-03). Not chosen: keep it in m2, or send [moq-rtc on rind](/quest/m1/rind/rtc.md) back to m2. m1's [moq-rtc on rind](/quest/m1/rind/rtc.md) requires this, so it sits at the m1 top level. It stays a child of the m2 [WebRTC epic](/quest/m2/webrtc/README.md). +Milestone: ✅ m1 (moved from m2, maintainer, 2026-11-03). Not chosen: keep it in m2, or send [moq-rtc on rind](/quest/m1/rind/rtc.md) back to m2. m1's [moq-rtc on rind](/quest/m1/rind/rtc.md) requires this, so it sits at the m1 top level. It stays a child of the m3 [WebRTC epic](/quest/m3/webrtc/README.md). - Vendor str0m and str0m-proto at the main-branch revision moq-dev/rind's `rind-str0m` targeted (`dc317173`, on dimpl 0.9 with str0m's pluggable crypto provider), with the dimpl, `is`, and sctp-proto versions it depends on (maintainer, 2026-10-31), so [moq-rtc on rind](/quest/m1/rind/rtc.md) can port rind's provider code unchanged. Commit them unchanged first so later diffs show only our changes, then trim. - Remove: str0m's `bwe/`, leaky pacer, H.266, RED, DTMF, G.7xx and comfort noise, VLA and simulcast layers, RTCP XR and app feedback, stats, `_internal_test_exports`, the crypto backends other than the one rind will replace (keep the provider trait until [moq-rtc on rind](/quest/m1/rind/rtc.md)); dimpl's `dtls13/` and `auto.rs`. Keep upstream's tests for what remains. -- Keep dimpl's typed `TimeoutError::Handshake` through the vendored `dtls.rs`, which str0m flattens into `CryptoError::Other(String)`, and replace moq-ice's text match for it with a typed match if [the typed DTLS timeout](/quest/m2/webrtc/dtls-timeout.md) has landed. +- Keep dimpl's typed `TimeoutError::Handshake` through the vendored `dtls.rs`, which str0m flattens into `CryptoError::Other(String)`, and replace moq-ice's text match for it with a typed match if [the typed DTLS timeout](/quest/m3/webrtc/dtls-timeout.md) has landed. - Keep the license files and record each upstream version in the module docs. - Drop the crates.io dependencies on str0m and friends from the workspace once nothing uses them. -Public API: none beyond what [rename](/quest/m1/webrtc-rename.md) changed. Wire: unchanged; the same DTLS 1.2 suites and SRTP profiles are offered. +Public API: none beyond what [rename](/quest/m2/webrtc-rename.md) changed. Wire: unchanged; the same DTLS 1.2 suites and SRTP profiles are offered. ## Required -- [Rename moq-rtc to moq-webrtc](/quest/m1/webrtc-rename.md) - the crate the stack is vendored into +- [Rename moq-rtc to moq-webrtc](/quest/m2/webrtc-rename.md) - the crate the stack is vendored into diff --git a/quest/m2/README.md b/quest/m2/README.md index 764a707aea7..88d6f5f7f1c 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -1,315 +1,189 @@ -# m2: later work +# m2: the next breaking release ## Goal -Independently shippable features, internal optimizations, and broad tooling -follow the clustering and API release. Publication and downstream adoption -also live here because they necessarily follow m1; they are not abandoned. +Every change that would need a semver-breaking release if it landed right +after the next cut of `main` into `release`, plus the [cut +gate](/quest/m2/cut-gate/README.md). The cut waits on this milestone alone; +complete it before cutting main into release. ## Plan -Decided 2026-10-13: a feature does not block the breaking release merely -because it was in the next-wave backlog. Keep existing behavior correct in -m1, and defer new capabilities without changing their intended outcome. -Dependencies on m1 remain explicit. An implementation that discovers a new -necessary API break brings that decision to the maintainer before proceeding. - -Decided 2026-11-03 (maintainer, Kixel's quest audit): [byte streams](/quest/m2/stream/README.md) -and the [mesh libraries](/quest/m2/mesh/README.md) rank first in m2, ahead -of [release execution](/quest/m2/release/README.md). Kixel's daemon builds on -them from `main` through a git submodule, so it needs them merged, not -released. They stay out of m1 so the cut does not wait on them; each starts -as soon as its m1 prerequisites (sockets, fastest-reader pacing, outbound -federation) land. - -Rate-grant work targets the next unpublished lite version after finalized -lite-07; bitrate enforcement is not part of this release. +Decided 2026-11-05 (maintainer, milestone re-cut): m2 holds the breaking half +of what was "everything before the cut" (2026-10-20). Breaking covers every +published surface, as the root [questline](/quest/README.md) defines: the +public Rust, JS, and bindings API, a frozen wire version, the hang catalog +JSON, a stored or exported container format, and CLI flags, config keys, and +environment variables. A change to lite-07-wip or to a `main`-only API the +cut would publish counts, because it could not land after the cut without +another breaking release. A non-urgent fix that breaks joins m2; an urgent +one joins m0. Placed in the re-cut: group-drops (its shape is open, but +naming abandoned groups on the wire lands on lite-07-wip) and the whole +unbounded-groups epic, whose additive compressed-stream child rides with it. + +The cut gates that break nothing (main no slower than release, vendored +fixes, the pre-cut audit re-run, and moq-c parity) live under the recurring +[cut gate](/quest/m2/cut-gate/README.md), decided the same day. + +Held by open claims: the m1 epics and quests marked below stay where they +are until their claims merge, and the [probe epic](/quest/m2/probe/README.md) +stays here while its padding claim is open, so the cut waits on it until the +[re-cut follow-up](/quest/m2/recut-held.md) moves it to m3. + +Carried from m1's Plan before the re-cut, where "m1" means the whole pre-cut +milestone, now m1 and m2: + +Decided with the maintainer on 2026-10-15: clustering stability and the +in-tree QUIC stack first. Decided 2026-10-20 (maintainer): m1 is everything +before the cut, not only breaking work, so ready non-breaking quests stay +here instead of moving out; the cut is what ships them. + +- Preserve epoch correctness, routing recovery, outbound federation, and + claim continuity on lite-07. Catalogs, long-lived readers, + and late joiners obey the same identity contract. +- Keep IETF passthrough, the API audit, the broad clock conversion, + archive replay/DVR correctness, and the TS fidelity + expansion in m1. Keep their correctness, interoperability, memory, and + performance evidence with them. +- Defer P2P, watch-worker planning and implementation, AMD Vulkan encode and + Intel VA-API/Vulkan import, and QoS lag and prefix stats to m2 with their + prerequisites. Their possible API breaks do not make them prerequisites of + this cut. Existing playback and A/V clock validation remain here. + Same-epoch importers were dropped (maintainer, 2026-10-19): a redundant + ingest pair runs on distinct epochs. +- Finalized lite-07 is preferred by first-party Rust and JS clients, with + older-version negotiation fallback. Servers accept it by default. Never + reuse a published identifier for an incompatible wire change; deferred + features use the appropriate subsequent wip/version if they need one. +- The next cut makes no new AMD/Intel GPU-input support promise. The later + multi-vendor release needs both hardware proofs before publication. +- Package publication, downstream adoption, and production rollout follow + the cut under [release execution](/quest/m3/release/README.md). + +Existing upgrade and identity guides carry migrations; feature docs change +inline. Keep generic proofs here and deployments and their operational +acceptance with the downstream operator. + +Keep one owner per shared code area and order prerequisites before consumers +(re-ranked in the 2026-10-20 audit: auth before cluster routing, and every +lite-07 prerequisite before those quests). +Decided 2026-10-25 (maintainer): the hand-written `moq-c` ships at this cut +with parity to moq-ffi for every m1 binding feature, so each binding quest +lands its C half there; the generated C line moves after the cut. +The moq-transport passthrough fields remain crate-private: no public moq-net +item exists only for moq-transport (maintainer, 2026-10-23). + +Added 2026-10-16: refresh, a breaking `Demand` change, so it lands before +the cut. + +Added 2026-10-22 (maintainer, from an external API audit): small breaks +that would otherwise force another breaking release (the FFI encoder config, +FromStr, dead items, `SessionClosed`, unprefixed C++), the hang draft's +warmup rule for the shipping dual decoder, the binding migration guide fixes, +and the API-diff tooling. Public routes now wait on cluster routing. + +Added 2026-10-20 (maintainer): the probe target, native probing, and the +native rung disable moved up from the [m2 probe epic](/quest/m2/probe/README.md), +so Rust, FFI, and OBS publishers recover a stopped rendition in this release; +padding and the browser's rung disable stay in m2, with only padding's +lite-07 stream type here. + +Added 2026-10-22 (maintainer, clustering audit): three interim fixes for +announce churn on today's hop-list mesh, shipping with the next cut from +`main` (not backported to `release`), so deployments get relief before the +route layer ships; and stats groups as +tracks, so per-group stats stop costing cluster announces. + +Added 2026-10-22 (maintainer, security audit of the relay, auth, stats, +ACME, and WebRTC): a clean close misreported as a revocation, injectable +metric tiers, an unbudgeted ACME renewal, unbounded mDNS work per WebRTC +offer, and an undocumented stats linger cut. The audit's `server_name` +finding was already fixed by moq-dev/moq#6509. + +Added 2026-10-23 (maintainer, from a linger audit): broadcasts lose their +finished state and retention moves to moq-mux, a break in every binding, so +it lands before the cut. + +Added 2026-10-23 (maintainer, from a moq-quic audit): moq-quic and its drivers +are unreleased, so their API is reshaped before the cut publishes it, and the +audit's receive-memory, priority, and lease bugs rank ahead of that reshape. + +Added 2026-10-23 (maintainer, pre-cut triage): breaks that would otherwise +force another major (`announce="never"`, the unused OBS outputs, binding +durations, and the remaining web-transport-trait adapters) land before the +cut, as do the small hostile-input and container fixes from the 2026-10-22 +security audit, and the stuck-window scan. + +Added 2026-10-24 (maintainer, from a moq-hls audit): import and export +hardening (URL redaction, ranged responses, redirect bases, sequence +arithmetic, DASH init readiness, dot-only names) and ffprobe segment +conformance; the audit's segment-finalization redesign is folded into +Catalog HLS field. + +Added 2026-10-24 (maintainer-requested pre-cut audit of main): remote +crashes and amplification in media and RTMP parsing, lite announce bounds, +JS track terminal causes, browser element teardown, and smaller Rust/JS +divergences, under one epic; its redesign proposals went to m2. + +Changed 2026-10-26 (maintainer): pure-Rust crypto moved to m3 until upstream +graviola and ACME releases make it cheap, so the cut ships on aws-lc-rs. +Dropping the `rsa` crate from moq-auth's production graph stays in m1. + +Added 2026-10-25 (maintainer): the studio's +GPU encode and source import quests are in m1 so +moq-video's GPU encode and import API changes, mainly encoders taking a GPU +surface and zero-copy texture import, land before the cut. + +Added 2026-10-27 (maintainer, from an external security audit): relay and +wire boundary fixes, importer streaming, moq-c handle wrap, browser input +checks, and CI tool pins, under one epic; its credential leaks went to m0. + +Added 2026-11-01 (maintainer): datagram tracks, so lite-07 freezes with +datagrams as their own track kind instead of single-frame groups. + +Added 2026-11-01 (maintainer, follow-up planning): byte-stream ladders, so +the binding API for `lower` breaks before the cut, `moq export` ending +with its broadcast, and a relay answering a SUBSCRIBE on a fetched copy. + +Added 2026-10-27 (maintainer, from an external release-to-main audit): the +bindings' silent `max_delay` default change and the upgrade notes that +contradict the code. Its other findings already had owners or contradicted +settled decisions (archives break in place; OBS video-only output stays +removed). + +Added 2026-11-01 (maintainer, follow-ups from the 2026-11-01 /quest-afk run): +the shared pacer's overshoot under 2 Mbit/s with the BBR3 retune it needs, +since BBR3 is the default controller the cut ships; a truncated MKV that +left its tracks open; and, under release performance, a bisect of the relay's +per-frame CPU growth since #5926. + +Added 2026-11-04 (maintainer): the relay reports the native sessions its +drain deadline force-closes while still open, apart from those only finishing +their end report, so an embedder's drain alert pages on real cuts. + +Decided 2026-11-05 (maintainer, /quest-audit): blockers rank above the +quests that require them. + +- ✅ Move the blockers up: Drop set and Subscribe ranges rank just above + Address groups by timestamp, and the API audit just above Cluster routing. +- Not chosen: moving the dependents down; leaving the order as it was. ## Required -- [Byte streams](/quest/m2/stream/README.md) - TCP connections ride MoQ losslessly through relays, proxied per hop rather than as IP packets -- [Mesh libraries](/quest/m2/mesh/README.md) - an `Endpoint` reaches any enrolled node by endpoint ID over relays or a sparse direct overlay, with address hints and a `.status` track; the mesh binary and UI live in Kixel -- [`@moq/net` broadcasts expose their requests](/quest/m2/net-broadcast-requests.md) - a JS broadcast serves tracks it never created, on demand, like Rust -- [`@moq/crypto` loads a stored signing key](/quest/m2/crypto-key-load.md) - one device key proves mesh identity and signs broadcasts -- [Announce credit](/quest/m2/announce-credit.md) - a subscriber bounds an Announce Stream's routes with credit at the wire, so a path flood never closes a session -- [JS announced coalescing](/quest/m2/js-announced-coalesce.md) - `@moq/net`'s `Announced` keeps one pending event per path, like Rust -- [An audio track's final flush joins its open group](/quest/m2/audio-flush-group.md) - a zero-`delay.max` subscriber gets the tail, not `Old` -- [Release execution](/quest/m2/release/README.md) - publication, installed-artifact proof, cleanup, and downstream adoption after m1 -- [Release pull requests read the R2 Rust cache](/quest/m2/mbx-r2-release-cache.md) - a release PR's `Check the cache` step reports effective read-only once the cut brings the cache to `release` -- [Binary release publishers run on their tag](/quest/m2/release-tag-publishers.md) - brew, Go and Swift releases stop running through `workflow_run` on main, once the cut brings the workflows to `release` -- [crates.io trusts the workflow](/quest/m2/crates-trusted-publisher.md) - maintainer action: the crates the cut first-publishes by token get a trusted publisher for `release-rs.yml` -- [Rust releases publish through OIDC](/quest/m2/release-rs-oidc.md) - release-plz publishes with trusted publishing and `CARGO_REGISTRY_TOKEN` is revoked -- [One policy for oversized container metadata](/quest/m2/import-metadata-policy.md) - fMP4 and MKV refuse or stream huge metadata by one documented rule -- [Wire fuzz coverage](/quest/m2/wire-fuzz-coverage.md) - the cmsg walks in moq-sock and moq-uring have invariant fuzz targets, and the unsafe peer input reaches runs under Miri -- [VA-API renderer tests](/quest/m2/vaapi-render-tests.md) - the VA-API renderer, decode, and transcode tests run in `just rs gpu` on AMD and Intel and fail instead of skipping, and hosted CI reports them ignored -- [One Ruff pin and Swift formatting on aarch64-linux](/quest/m2/format-gate-followups.md) - only the dev shell pins Ruff, and aarch64-linux checks Swift formatting once nixpkgs builds `swiftc` there -- [Weekly mutation testing on critical modules](/quest/m2/mutants.md) - cargo-mutants runs weekly on moq-auth and moq-net's permission, resume, and expiry code -- [Video quality](/quest/m2/video-quality/README.md) - a nightly VMAF harness grades every encoder backend and on-demand GoP pops against floors, and moq-boy's encode is fixed under it -- [P2P](/quest/m2/p2p/README.md) - application-selected peer sessions use shared priorities, routing, and same-epoch handover -- [moq-auth drops the unused peer grant API](/quest/m2/auth-drop-peer-grant.md) - P2P trusts its peers, so `PeerGrant` and its `KeySet` methods go -- [rust2's exporter is ready for moq](/quest/m2/rust2-exporter.md) - waiting on moq-dev/rust2's exporter to generate every language moq ships -- [Switch to rust2's exporter](/quest/m2/ffi-exporter.md) - moq's bindings come from rust2-ffi, moq-ffi shrinks to its remainder, and moq's UniFFI generator code is deleted -- [Generated C bindings](/quest/m2/c/README.md) - C generated from moq-ffi ships as `moq-c` at a later cut's shared minor and replaces the hand-written crate -- [A C origin can discover eagerly, like a relay](/quest/m2/c-origin-relay.md) - the C API puts an origin in relay mode, so forwarding a client session's routes needs no local announce watcher -- [A runtime-free QUIC driver](/quest/m2/quic-sansio-driver.md) - a caller's own loop moves UDP datagrams and polls moq sessions over moq-quic, for rust2's bindings -- [Benchmark sources](/quest/m2/bench-sources.md) - every measuring nightly benchmark feeds the regression table, and none is a smoke run -- [QoS](/quest/m2/qos/README.md) - the relay's egress `lag` histogram and `dropped` counters on the stats totals and prefix tracks -- [HLS and DASH browser playback](/quest/m2/hls-player-test.md) - hls.js and dash.js play, reload, switch, and survive reconfiguration nightly -- [The DASH manifest keeps segments across a reconfigure](/quest/m2/dash-reconfigure.md) - a same-codec reconfigure keeps the old instance's segments listed in DASH, as HLS does -- [Broadcast fairness](/quest/m2/broadcast-fairness.md) - broadcasts share a cluster link fairly, so one tenant's priority never starves another's -- [Cache fair share](/quest/m2/cache-fairness.md) - one tenant cannot crowd another out of the relay's shared group cache -- [Peer grant bound](/quest/m2/peer-grant-bound.md) - a peer's AUTH_OK costs near-linear time in its bytes on every input shape, in Rust and in a browser -- [A regrant re-checks only the routes it can change](/quest/m2/regrant-route-recheck.md) - an `AUTH_OK` no longer costs routes times grant members on every lite announce stream -- [Plan: watch worker](/quest/m2/plan-watch-worker.md) - prototype an invisible page worker against app-spawned workers, and land the jank harness that decides -- [Watch worker](/quest/m2/watch-worker.md) - watch playback runs in a worker onto an OffscreenCanvas, so main-thread jank never stalls video or audio -- [Vulkan Video encode on AMD](/quest/m2/vulkan-encode.md) - H.264 and H.265 from an external Vulkan image on RADV, hand-rolled on ash, proven on an RX 9070 -- [VA-API encodes an external Vulkan image](/quest/m2/vaapi-vulkan-import.md) - an explicit-sync DMA-BUF reaches Intel's encoder, proven on Arrow Lake -- [C++ FFI reuse](/quest/m2/cpp-ffi-reuse.md) - C++ packages link the shared default-feature FFI build once it is proven compatible -- [Upstream reports](/quest/m2/upstream-reports.md) - report the faad, retina, and mr-boxington bugs found before the cut - -- [Native compression flush](/quest/m2/native-compression-flush.md) - report the per-frame nonfinal flush requirement in existing browser discussions -- [Native synchronous codecs](/quest/m2/native-compression-sync.md) - report the stateful small-frame synchronous API requirement -- [Native browser codecs](/quest/m2/native-compression-adopt.md) - adopt native operations when timing, frame and resource contracts hold - -- [moq-net's library tests pass under cargo test](/quest/m2/net-test-subscriber.md) - two moq-net tests stop each installing a global tracing subscriber, so plain `cargo test -p moq-net --lib` passes - -- [OBS native codecs](/quest/m2/obs-moq-video/README.md) - replace FFmpeg video and audio decoding with moq-video and moq-audio, deliver GPU frames, and use native audio/video encoders -- [MoQ in obs-studio](/quest/m2/obs-studio/README.md) - a native MoQ output and service merged into obs-studio, once its maintainers agree; the plugin carries it until then -- [AudioToolbox decode](/quest/m2/audio-decode-audiotoolbox.md) - macOS and iOS decode HE-AAC, multichannel AAC, and what else the framework offers -- [AudioToolbox encode](/quest/m2/audio-encode-audiotoolbox.md) - macOS and iOS encode AAC-LC -- [GPU CI](/quest/m2/gpu-ci.md) - NVIDIA tests gate the merge queue on a self-hosted GPU runner VM, and `just rs nvidia` runs them locally instead of skipping -- [Vendor-free CARLA bridge](/quest/m2/carla-bridge.md) - the CARLA demo's GPU bridge lets moq-video pick the encoder, and its stand-in test runs on AMD as well as NVIDIA -- [Probe](/quest/m2/probe/README.md) - a session probes up to the bitrate it wants to send or receive, so a stopped simulcast rendition resumes and a viewer up-switches; the browser pads where native sessions retransmit -- [Media stats](/quest/m2/stats/README.md) - publishers announce a stats track in the catalog, viewers answer a soliciting catalog through a per-catalog `.echo` broadcast, and one model turns both into a health verdict and a preflight report -- [Perf](/quest/m2/perf/README.md) - eliminate measured hot-path costs across moq-uring, kio, and the moq-net model -- [Wire stats](/quest/m2/wire-stats/README.md) - `Presence` counts each root's transport bytes on the wire, `wire_tx` and `wire_rx`, from QUIC, WebSocket, and embedder gateway sources -- [Session outcome records](/quest/m2/session-outcome-records.md) - relay stats publish each refusal and abnormal session end as a record per label, bounded under a flood, beside the counters -- [Performance survey follow-ups](/quest/m2/performance-survey/README.md) - benchmark the source audit's transport, browser, media and serving risks before optimizing -- [Transport x version benches](/quest/m2/bench-transport-sweep.md) - the session benches sweep transports as well as versions -- [Shared group serving and ingest](/quest/m2/shared-serve.md) - Rust's moq-lite and moq-transport sessions serve and ingest groups through one poll machine each, with only wire encoding per protocol -- [Shared group serving and ingest in JS](/quest/m2/shared-serve-js.md) - the same split in js/net, following the Rust seam -- [Paired bench BASE](/quest/m2/bench-base-paired.md) - `just bench ` uses the nightly's paired comparison and the old one is deleted -- [Audio renditions carry a language](/quest/m2/audio-lang.md) - audio renditions have an optional BCP-47 `lang`, and watch auto-picks within one language -- [fMP4 and TS imports publish BCP-47 languages](/quest/m2/import-lang-iso639.md) - ISO 639-2 codes become `en`-style tags on audio and text -- [HLS carries every audio language](/quest/m2/hls-audio-languages.md) - every `EXT-X-MEDIA` audio entry imports with its `LANGUAGE`, and exports write it back -- [Receive pool](/quest/m2/receive-pool.md) - one byte budget per worker covers every connection's receive credit and the cache, billing each frame once -- [Front parking](/quest/m2/origin-front-parks.md) - an unroutable request waits on a front instead of re-asking on every route-table move -- [A refused follower asks a replacement handler](/quest/m2/follow-refused-retry.md) - a same-instance handler swap with identical route details re-asks a refused `Following`, while listeners still see no change -- [Route wakes](/quest/m2/route-wakes.md) - a route change wakes only the fronts it can move, so pool churn stops scaling with served paths -- [A route stream's interest is a set of prefixes](/quest/m2/route-interest-prefixes.md) - one Announce Stream covers several subtrees, with floors and certification proved over the set -- [A socket dial learns its peer is behind an older hop](/quest/m2/socket-old-hop-signal.md) - a relay finds the dialed endpoint behind its older moq-lite session and marks that path, so the dial fails `Unsupported` while one to an absent peer still waits -- [Fewer allocations in announce fan-out](/quest/m2/announce-fanout-allocs.md) - a deep path costs no more allocations per subscriber than a shallow one -- [moq-room scales to large rooms](/quest/m2/room-bench.md) - a benchmark measures `Room` with large participant counts, and polling narrows only if it shows a slope -- [Route health](/quest/m2/route-health/README.md) - epoch-only active/passive track recovery over metadata-only subscriptions -- [Wrapper traits over moq-net](/quest/m2/net-wrap/README.md) - moq-net exports producer and consumer traits, and every writer and reader above it takes them, so a wrapper such as e2ee passes through unchanged -- [E2EE](/quest/m2/e2ee/README.md) - TypeScript and Rust peers interoperate over encrypted broadcasts no relay can decrypt -- [Content protection](/quest/m2/drm/README.md) - Common Encryption CMAF publishes unchanged, signalled in the hang `drm` section and MSF `contentProtections`, with license URLs from Rust, the CLI, and every binding -- [iOS capture](/quest/m2/mobile-capture-ios.md) - Rust captures the camera and screen on iOS, setting the catalog rotation -- [Android capture](/quest/m2/mobile-capture-android.md) - Rust captures through NDK/JNI on Android, reusing the existing codecs and setting the catalog rotation -- [Latest readers use Range::live()](/quest/m2/readers-range-live.md) - after #6278, readers start at the live edge without waiting on `largest()` -- [Audio outlives video](/quest/m2/audio-bufferbloat-av.md) - under bufferbloat audio stays within budget while video may skip, rendered frames stay in sync, and native audio rows are enforced -- [ViSQOL grading](/quest/m2/audio-visqol.md) - the nightly scores played audio against a reference clip and fails below measured floors -- [PulseAudio capture periods](/quest/m2/pulseaudio-capture-period.md) - capture on cpal's PulseAudio host arrives in short periods, not the server's 2 s default fragment, proven on the null sink's monitor -- [Bindings size profile](/quest/m2/ffi-size-profile.md) - a benchmark decides whether the moq-ffi builds ship at opt-level "s", which halves the dylib -- [Value merge-patch diff](/quest/m2/json-value-diff.md) - benchmarks decide between moq-json's generic serializer diff, a ported `Value` diff, and compression alone -- [Measure what a catalog republish costs per rendition edit](/quest/m2/catalog-republish-cost.md) - bench whole-catalog re-serialization across track counts, then decide deltas or a bound -- [A JSON snapshot consumer resyncs after a bad frame](/quest/m2/json-snapshot-resync.md) - a decode failure drops the group with a typed error, so `@moq/room` and moq-boy resume at the next snapshot -- [Go module proxy](/quest/m2/go-module-proxy.md) - `moq.dev/moq-ffi` ships from a static GOPROXY we host, so its staticlibs stop growing git history by ~61 MiB per release -- [Go per-platform lib modules](/quest/m2/go-ffi-platform-modules.md) - a Go build downloads only the host's staticlib, and `go mod vendor` works -- [Dart on iOS](/quest/m2/dart-ios.md) - prove the shipped iOS native asset actually loads on a device, which no CI can -- [Mobile completion](/quest/m2/mobile-completion.md) - verify the Swift and Kotlin bindings over Rust-owned capture -- [Browser publishing paths under test](/quest/m2/publish-firefox.md) - the media harness publishes from Firefox in Nightly and passes, covering the `