From 22f356596a69dd87bf26ce80894f1019472b6293 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 14 Nov 2026 12:08:29 -0800 Subject: [PATCH 1/3] quest: punt m2's non-breaking quests so main can be cut Move route acceptance and the request loop to m3's cluster-routing epic, media consumers to m3, moq-transport time addressing to m4, and the Playwright bump to m1; remove the E2EE nonce quest, folding its draft wording into lite-07 by start; split group drops' lite-07 wire question into its own quest that starts now; let catalog-at-timestamp wait only on the Rust model; shrink the bindings to the rename that remains. Co-Authored-By: Claude Opus 5.5 --- .../cluster-routes => m1}/playwright-pin.md | 8 ++ quest/m2/README.md | 31 +++++++ quest/m2/catalog-at-timestamp.md | 11 ++- quest/m2/cluster-routes/README.md | 6 +- quest/m2/cluster-routes/flapping-publisher.md | 2 +- quest/m2/cluster-routes/switch.md | 2 +- quest/m2/group-drops-wire.md | 64 +++++++++++++ quest/m2/group-drops.md | 89 ++++++------------- quest/m2/lite07-finalize.md | 30 ++++++- quest/m2/time-addressing/bindings.md | 13 ++- quest/m2/time-addressing/e2ee.md | 21 ----- quest/m2/time-addressing/lite07.md | 9 ++ quest/m2/time-addressing/model.md | 2 +- .../cluster-routing}/acceptance.md | 12 +++ quest/m3/cluster-routing/federation.md | 4 +- .../cluster-routing}/request-loop.md | 6 ++ .../time-addressing-consumers.md} | 34 +++++-- quest/m4/cluster-fault-schedules.md | 2 +- quest/m4/ietf-range-fetch.md | 4 +- .../ietf.md => m4/ietf-time-addressing.md} | 12 ++- quest/m5/e2ee/README.md | 2 +- quest/m5/routes-browser-proof.md | 4 +- 22 files changed, 258 insertions(+), 110 deletions(-) rename quest/{m2/cluster-routes => m1}/playwright-pin.md (83%) create mode 100644 quest/m2/group-drops-wire.md delete mode 100644 quest/m2/time-addressing/e2ee.md rename quest/{m2/cluster-routes => m3/cluster-routing}/acceptance.md (89%) rename quest/{m2/cluster-routes => m3/cluster-routing}/request-loop.md (86%) rename quest/{m2/time-addressing/consumers.md => m3/time-addressing-consumers.md} (50%) rename quest/{m2/time-addressing/ietf.md => m4/ietf-time-addressing.md} (76%) diff --git a/quest/m2/cluster-routes/playwright-pin.md b/quest/m1/playwright-pin.md similarity index 83% rename from quest/m2/cluster-routes/playwright-pin.md rename to quest/m1/playwright-pin.md index e2b41f3d2f9..66342e444c0 100644 --- a/quest/m2/cluster-routes/playwright-pin.md +++ b/quest/m1/playwright-pin.md @@ -21,6 +21,14 @@ nixpkgs still carries 1.64.1. ## Plan +Moved from m2 to m1 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): ✅ m1, since a toolchain bump breaks +nothing and builds on no m2 work (rejected: m2, where the cut waited on +nixpkgs; m4 or m5, which hold it behind the cut or the next wire cut once +nixpkgs lands). This replaces the 2026-11-06 decision below that the lite-07 +cut waits for the bump: [lite07-finalize](/quest/m2/lite07-finalize.md) +instead runs the lane once with npm's Playwright 1.65.0 before the rename. + Decided 2026-11-06 (maintainer, /quest-complete, on Pullfrog's review of [moq-dev/moq#8037](https://github.com/moq-dev/moq/pull/8037)): ✅ bump Playwright, and the lite-07 cut waits for it. Not chosen: running installed diff --git a/quest/m2/README.md b/quest/m2/README.md index 2580538bf1c..cd6699fe775 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -217,3 +217,34 @@ rule here). Its lag rule reshapes `main`-only API the cut would publish (the `stretch` setting, moq-audio's `Sink::due` and `bus::Positioned`), and the cut should not ship the 2026-11-09 stretch model, which lets audio trail video by up to 2 s. + +Decided 2026-11-14 (m2 triage before the cut, under /quest-afk, for the +maintainer's review; the maintainer asked that what remains be unblocked or +punted). m2 keeps only what would need a breaking release had it landed right +after the cut: + +- ✅ Left m2: [route acceptance](/quest/m3/cluster-routing/acceptance.md) + and [the request loop](/quest/m3/cluster-routing/request-loop.md) to m3's + cluster-routing epic (tests and fixes, no wire); + [media consumers](/quest/m3/time-addressing-consumers.md) to m3 (its API + breaks ride the model; dropping hang's markers is tolerated by readers); + [moq-transport time addressing](/quest/m4/ietf-time-addressing.md) to m4 + (low-priority compatibility, no named consumer); and the + [Playwright bump](/quest/m1/playwright-pin.md) to m1, with + lite07-finalize checking Chromium 158 once by hand instead. The E2EE nonce + quest was removed: the nonce already binds the wire ID, which becomes the + start, and lite-07 by start rewords the draft. Rejected for each: staying + in m2. +- ✅ Stayed in m2 though not breaking itself: + [the interest set](/quest/m2/cluster-routes/interest-set.md), because + [the route stream](/quest/m2/cluster-routes/route-stream.md) needs it. + The route stream stays because lite-07 would otherwise freeze with one + router key per announce stream, which the route model doesn't check, and + keep the reopen-and-hand-over machinery for its lifetime (rejected: moving + both to lite-08). +- ✅ [Group drops](/quest/m2/group-drops.md) split: its lite-07 wire question + is [its own quest](/quest/m2/group-drops-wire.md), which starts now and + gates the freeze; the public `Ordered` API waits for the model. + [Catalog at timestamp](/quest/m2/catalog-at-timestamp.md) no longer waits + for `@moq/net` by start, and [the bindings](/quest/m2/time-addressing/bindings.md) + shrink to a rename, since the model already fills each field with the start. diff --git a/quest/m2/catalog-at-timestamp.md b/quest/m2/catalog-at-timestamp.md index b1f883cf3af..031207dd2ba 100644 --- a/quest/m2/catalog-at-timestamp.md +++ b/quest/m2/catalog-at-timestamp.md @@ -27,7 +27,16 @@ until media reaches that time; one that reads it late applies it at once. A scale-less broadcast's catalog has no media time to wait for, so it applies on arrival, as today. +Decided 2026-11-14 (the m2 triage before the cut, under /quest-afk, for the +maintainer's review): ✅ this waits only for the Rust model, not for +[@moq/net by start](/quest/m2/time-addressing/js.md) (rejected: keeping +that wait). A catalog's stamp is its frame's timestamp, which `@moq/net` +frames already carry (moq-json's `Timed.at`), and nothing here reads a group +start. The JS half checks that `js/hang`'s catalog producer stamps from the +broadcast clock, and makes it do so if not. It stays in m2: `rs/hang` and +`js/hang` return the stamp with each catalog, a breaking change to both +consumers, and the hang draft's rule is what lite-07 catalogs mean. + ## Required - [Rust groups are addressed by their start](/quest/m2/time-addressing/model.md) - the catalog producer stamps from the broadcast clock -- [@moq/net addresses groups by start](/quest/m2/time-addressing/js.md) - the same for js/hang diff --git a/quest/m2/cluster-routes/README.md b/quest/m2/cluster-routes/README.md index 4f9c28e3070..69f8607797d 100644 --- a/quest/m2/cluster-routes/README.md +++ b/quest/m2/cluster-routes/README.md @@ -57,11 +57,11 @@ The items below were decided 2026-11-10 (maintainer, /quest-plan on lite-07 rout Measured on 24 relays (the mesh sweep's sparse shape, 16 seeds), against today's router, with the doubt lasting 4 hops of delay: a detour settles in 12 hops of delay where the distance takes 15.7, and in 6.2 where it does not run through the far end of the closed link; the publisher's relay dying costs 124 route messages where the distance costs 276, with no loop and 6 claims sent again; and a link closing in a clique costs 44 messages with one publisher behind it and 198 with eight, where the distance costs 621 and 5,024. Accepted: a detour through the far end of a closed link waits the timer out; selected routes can loop for a moment when two unrelated things fail at once (32 of 120,000 churn steps), which the distance never does; and holds and doubt have passed sweeps. The model covers both, but its no-stale-route property holds only for one failure and a patient timer; `StaleIsChased` bounds the rest. The timer's length is the model's and the router's to settle, from the maintainer's 1 s. Rejected: Babel's distance; paths with nothing else, which hunt through stale paths (65,219 messages for one publisher leaving a clique of 12); no doubt, which loops when a relay with several neighbours dies; and a doubt lifted by an epoch the node floods, which resolves in a couple of hops but costs a message per session on each relay-to-relay close ("Epoches are a bit scary in terms of messages"). -28. ✅ Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel), asked how item 27's removal is split and ordered: **the router first with no wire change, then a switch of the sessions, and the switch lands before the route stream.** [The router](https://github.com/moq-dev/moq/pull/8622) runs the path rule with a route per scope, sans-IO, beside today's router. [The switch](/quest/m2/cluster-routes/switch.md) puts it on the lite-07-wip wire, the draft, the Rust sessions, and `js/net`, and deletes Babel's router. [The interest set](/quest/m2/cluster-routes/interest-set.md) then edits the path router only, and [the route stream](/quest/m2/cluster-routes/route-stream.md) follows the switch with no echo or route request to carry. The switch's recommended wire puts the answer that ends a hold on the publisher half, behind the routes its sender sent first, so the path rule needs no order between streams that today's sessions lack for one prefix. [Acceptance](/quest/m2/cluster-routes/acceptance.md) is of the switched sessions, and the inductive invariant stays in m1, rewritten for the path, without `LoopFree` as an invariant. Rejected: the router quest in m1; one quest for router, wire, draft, sessions, and `js/net`; the route stream first, which builds the echo and ROUTE_REQUEST on the new stream and then deletes them; one wire change for the path rule and the one stream together; moving the inductive invariant to m4; deleting it. Reversed 2026-11-13 (maintainer, /quest-complete): ✅ the inductive invariant is deleted, since Apalache cannot step even one transition of the route model ([moq-dev/moq#8564](https://github.com/moq-dev/moq/pull/8564)), no Rust TLA+ checker qualifies ([moq-dev/moq#8600](https://github.com/moq-dev/moq/pull/8600), [moq-dev/moq#8669](https://github.com/moq-dev/moq/pull/8669)), and no more JVM model checking is wanted here (rejected: keeping it paused). +28. ✅ Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel), asked how item 27's removal is split and ordered: **the router first with no wire change, then a switch of the sessions, and the switch lands before the route stream.** [The router](https://github.com/moq-dev/moq/pull/8622) runs the path rule with a route per scope, sans-IO, beside today's router. [The switch](/quest/m2/cluster-routes/switch.md) puts it on the lite-07-wip wire, the draft, the Rust sessions, and `js/net`, and deletes Babel's router. [The interest set](/quest/m2/cluster-routes/interest-set.md) then edits the path router only, and [the route stream](/quest/m2/cluster-routes/route-stream.md) follows the switch with no echo or route request to carry. The switch's recommended wire puts the answer that ends a hold on the publisher half, behind the routes its sender sent first, so the path rule needs no order between streams that today's sessions lack for one prefix. [Acceptance](/quest/m3/cluster-routing/acceptance.md) is of the switched sessions, and the inductive invariant stays in m1, rewritten for the path, without `LoopFree` as an invariant. Rejected: the router quest in m1; one quest for router, wire, draft, sessions, and `js/net`; the route stream first, which builds the echo and ROUTE_REQUEST on the new stream and then deletes them; one wire change for the path rule and the one stream together; moving the inductive invariant to m4; deleting it. Reversed 2026-11-13 (maintainer, /quest-complete): ✅ the inductive invariant is deleted, since Apalache cannot step even one transition of the route model ([moq-dev/moq#8564](https://github.com/moq-dev/moq/pull/8564)), no Rust TLA+ checker qualifies ([moq-dev/moq#8600](https://github.com/moq-dev/moq/pull/8600), [moq-dev/moq#8669](https://github.com/moq-dev/moq/pull/8669)), and no more JVM model checking is wanted here (rejected: keeping it paused). -29. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), asked how the path rule keeps the `upstream` guarantee, which the prototype left out and [the switch](/quest/m2/cluster-routes/switch.md) had listed for removal with Babel's machinery: **a route keeps one sticky down-only flag beside its path.** A relay sets it on a route it learns over a link marked `upstream`, it is never cleared on a later hop, and a relay never sends a flagged route over an upstream link. The flag is export policy, not loop avoidance, so the path does not replace it: a relay that hears a CDN route from a LAN peer learned it on a link that is not upstream, and only the flag tells it the route came down from an upstream. That case is a local cluster with more than one uplink ([outbound federation](/quest/m3/cluster-routing/federation.md)), where a relay whose own uplink died reaches the CDN through a peer; an edge that dials only its cores needs just the local rule. This is the Only-To-Customer attribute of BGP roles (RFC 9234). The router (`rs/moq-net/src/route/path.rs`, built in [#8622](https://github.com/moq-dev/moq/pull/8622)) carries the flag and its export check, [the switch](/quest/m2/cluster-routes/switch.md) adds them to `RouteHandoff.tla` and keeps the flag on ROUTE_START and ROUTE_UPDATE, and [acceptance](/quest/m2/cluster-routes/acceptance.md)'s two-uplink mesh proves it. Sender side only, as today. Rejected: a mark on each hop of the path, which gives the same answer from more bytes and model state; the local rule with no flag, which either leaks through a LAN peer or gives up the dead-uplink fallback; also refusing a flagged route that arrives from a link whose grant marks the sender as a customer, which can be added later without a wire change. +29. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), asked how the path rule keeps the `upstream` guarantee, which the prototype left out and [the switch](/quest/m2/cluster-routes/switch.md) had listed for removal with Babel's machinery: **a route keeps one sticky down-only flag beside its path.** A relay sets it on a route it learns over a link marked `upstream`, it is never cleared on a later hop, and a relay never sends a flagged route over an upstream link. The flag is export policy, not loop avoidance, so the path does not replace it: a relay that hears a CDN route from a LAN peer learned it on a link that is not upstream, and only the flag tells it the route came down from an upstream. That case is a local cluster with more than one uplink ([outbound federation](/quest/m3/cluster-routing/federation.md)), where a relay whose own uplink died reaches the CDN through a peer; an edge that dials only its cores needs just the local rule. This is the Only-To-Customer attribute of BGP roles (RFC 9234). The router (`rs/moq-net/src/route/path.rs`, built in [#8622](https://github.com/moq-dev/moq/pull/8622)) carries the flag and its export check, [the switch](/quest/m2/cluster-routes/switch.md) adds them to `RouteHandoff.tla` and keeps the flag on ROUTE_START and ROUTE_UPDATE, and [acceptance](/quest/m3/cluster-routing/acceptance.md)'s two-uplink mesh proves it. Sender side only, as today. Rejected: a mark on each hop of the path, which gives the same answer from more bytes and model state; the local rule with no flag, which either leaks through a LAN peer or gives up the dead-uplink fallback; also refusing a flagged route that arrives from a link whose grant marks the sender as a customer, which can be added later without a wire change. -30. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), after a survey of BGP, EIGRP, and their successors against item 27: most of the path rule already matches that prior art (AS_PATH loop detection, root-cause withdrawal, graceful restart, End-of-RIB, outbound route filtering, and item 29's Only-To-Customer flag). Three gaps are taken, all in [the switch](/quest/m2/cluster-routes/switch.md) and [acceptance](/quest/m2/cluster-routes/acceptance.md): **a dead-hop message on a scoped session applies only to the routes heard on that session and casts no doubt**, since in BGP a neighbour withdraws only what it sent, and a scoped peer (a federated relay, later a browser) could otherwise name a core hop it only read in a path and drop healthy routes outside its scope; **holds are bounded in time**, a neighbour's missing answer counting as nothing after a deadline, and a session whose announce stream has stopped draining is closed, which avoids EIGRP's stuck-in-active and BGP's zombie routes (RFC 9687), and is safe because a hold protects presence, not loop freedom; and **three tests before any design change**: neighbours noticing a dead relay up to the 3 s keep-alive apart (to size the doubt timer, measured in hops of delay today), a three-relay priority dispute wheel (RFC 4264's wedgies, since priority ranks above cost), and a primary that fails and returns. No wire bytes change; the first defines what the dead-hop message means. Rejected: declaring the link relation in SETUP and refusing leaked routes on receipt (RFC 9234), since the accepting side already knows the relation from its grant and it adds wire for a misconfiguration; MRAI and route-flap damping, which exist because BGP delays announcements; link state; per-hop signatures. +30. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), after a survey of BGP, EIGRP, and their successors against item 27: most of the path rule already matches that prior art (AS_PATH loop detection, root-cause withdrawal, graceful restart, End-of-RIB, outbound route filtering, and item 29's Only-To-Customer flag). Three gaps are taken, all in [the switch](/quest/m2/cluster-routes/switch.md) and [acceptance](/quest/m3/cluster-routing/acceptance.md): **a dead-hop message on a scoped session applies only to the routes heard on that session and casts no doubt**, since in BGP a neighbour withdraws only what it sent, and a scoped peer (a federated relay, later a browser) could otherwise name a core hop it only read in a path and drop healthy routes outside its scope; **holds are bounded in time**, a neighbour's missing answer counting as nothing after a deadline, and a session whose announce stream has stopped draining is closed, which avoids EIGRP's stuck-in-active and BGP's zombie routes (RFC 9687), and is safe because a hold protects presence, not loop freedom; and **three tests before any design change**: neighbours noticing a dead relay up to the 3 s keep-alive apart (to size the doubt timer, measured in hops of delay today), a three-relay priority dispute wheel (RFC 4264's wedgies, since priority ranks above cost), and a primary that fails and returns. No wire bytes change; the first defines what the dead-hop message means. Rejected: declaring the link relation in SETUP and refusing leaked routes on receipt (RFC 9234), since the accepting side already knows the relation from its grant and it adds wire for a misconfiguration; MRAI and route-flap damping, which exist because BGP delays announcements; link state; per-hop signatures. The route layer's core landed in [moq-dev/moq#7676](https://github.com/moq-dev/moq/pull/7676): a diff --git a/quest/m2/cluster-routes/flapping-publisher.md b/quest/m2/cluster-routes/flapping-publisher.md index 91be8728939..960b68df961 100644 --- a/quest/m2/cluster-routes/flapping-publisher.md +++ b/quest/m2/cluster-routes/flapping-publisher.md @@ -64,4 +64,4 @@ Work: ## Related -- [A request loop heals once routes settle](/quest/m2/cluster-routes/request-loop.md) - another failure mode from the same BGP comparison +- [A request loop heals once routes settle](/quest/m3/cluster-routing/request-loop.md) - another failure mode from the same BGP comparison diff --git a/quest/m2/cluster-routes/switch.md b/quest/m2/cluster-routes/switch.md index 4cc9ed91e02..a3d35a641e0 100644 --- a/quest/m2/cluster-routes/switch.md +++ b/quest/m2/cluster-routes/switch.md @@ -168,4 +168,4 @@ Public API: none expected. Wire: lite-07-wip only. ## Related - [Each side says everything about routing on one stream](/quest/m2/cluster-routes/route-stream.md) - moves these messages onto one stream per side afterwards -- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - proves the switched sessions end to end +- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - proves the switched sessions end to end diff --git a/quest/m2/group-drops-wire.md b/quest/m2/group-drops-wire.md new file mode 100644 index 00000000000..d20faf15772 --- /dev/null +++ b/quest/m2/group-drops-wire.md @@ -0,0 +1,64 @@ +# [M] A moq-lite subscriber always learns which group it abandoned + +## Goal + +No group a moq-lite subscriber gives up on vanishes because its stream was +stopped or evicted before its header was read: the subscriber always learns +the ID of a group it abandoned. moq-transport reports what its wire allows, +and the PR records any gap there. Whether this needs a lite-07 wire change is +settled before lite-07 freezes. + +## Plan + +Split 2026-11-14 from [the public drop signal](/quest/m2/group-drops.md) (the +m2 triage before the cut, under /quest-afk, for the maintainer's review): +✅ the wire half reads no group key, so it starts now, and +[lite-07's freeze](/quest/m2/lite07-finalize.md) waits on it instead of on +the public API (rejected: keeping one quest, which holds this wire question +until the Rust model lands). + +Planned 2026-11-04 with the maintainer, from +[moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838). Under that +benchmark's overload policy, overcommitted cells hang. Sometimes the subscriber +drops a group without `recv_group` ever returning it: either the group's stream +was evicted before its header was read, or the group was evicted and so was the +FETCH that refetched it. The 4 MiB-frame cell hits this on every run; the +256-stream cell sometimes does. + +✅ **The wire mechanism is this quest's call, with numbers** (maintainer, +2026-11-04). Compare: + +- **The publisher answers STOP_SENDING with SUBSCRIBE_DROP.** Lite already + sends SUBSCRIBE_DROP on the control stream when a group fails at the + publisher (`GroupServe::settle_failed`, `rs/moq-net/src/lite/publisher.rs`, + versions with a track stream), but a subscriber's STOP_SENDING doesn't + produce one. +- **The subscriber reads a group's header before it stops or evicts that + stream.** + +Doing both is fine if each is needed. Start with the maintainer's question: +why does the subscriber stop or evict a stream before reading its header at +all? If receive-window eviction can wait for the header, take the no-wire +path and remove this quest from +[lite07-finalize](/quest/m2/lite07-finalize.md)'s Required. + +Take the numbers from the receive-windows benchmark's overcommitted cells (256 +streams, 4 MiB frames, follow; `rs/moq-tokio/tests/integration/receive_credit.rs`): +each must account for every group sent as delivered or abandoned, counted +inside moq-net until [the public drop signal](/quest/m2/group-drops.md) lets +the benchmark count them itself. Compare their throughput and the +control-stream bytes each mechanism adds. Cover moq-transport too, or say why +it differs. A wire rule applies to `js/net`'s publisher and subscriber in the +same PR. + +The drop set owns the per-cursor drop runs and their reasons +([moq-dev/moq#8476](https://github.com/moq-dev/moq/pull/8476)); this changes +only whether an abandoned group is known, not how a cursor judges a missing +one. + +Public API: none. Wire: possibly lite-07-wip (SUBSCRIBE_DROP for a stopped +group), decided here. + +## Related + +- [The public drop signal](/quest/m2/group-drops.md) - surfaces what this makes known to the application diff --git a/quest/m2/group-drops.md b/quest/m2/group-drops.md index 1d74fb8506b..45d11313061 100644 --- a/quest/m2/group-drops.md +++ b/quest/m2/group-drops.md @@ -1,81 +1,46 @@ -# [M] A group a subscriber gives up on is always reported +# [S] A group a subscriber gives up on is always reported ## Goal -Every group a moq-lite subscriber gives up on surfaces to the application: no -group vanishes because its stream was stopped or evicted before its header was -read. On the wire, the subscriber always learns the sequence of a group it -abandoned; moq-transport reports what its wire allows, and the PR records any -gap there. +Every group a moq-lite subscriber gives up on surfaces to the application. In the API, `track::Subscriber`'s drop signal (today the crate-private `poll_drop`, which the ordered reader and resume use to skip gaps) is public, so the receive-windows benchmark and applications can count losses instead of -waiting forever. +waiting forever, and that benchmark's overcommitted cells finish with +`delivered_frames` plus the reported drops accounting for every group sent. ## Plan Planned 2026-11-04 with the maintainer, from -[moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838). Under that -benchmark's overload policy, overcommitted cells hang. Sometimes the subscriber -drops a group without `recv_group` ever returning it: either the group's stream -was evicted before its header was read, or the group was evicted and so was the -FETCH that refetched it. No public API reports that group, so a reader that -paces on delivered-or-evicted groups stalls. The 4 MiB-frame cell hits this on -every run; the 256-stream cell sometimes does. +[moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838): no public API +reports a group the subscriber dropped without `recv_group` returning it, so a +reader that paces on delivered-or-evicted groups stalls. Split 2026-11-14 (the +m2 triage before the cut, under /quest-afk, for the maintainer's review): +[the wire half](/quest/m2/group-drops-wire.md) makes every abandoned group +known and decides lite-07's part; this publishes it. It stays in m2 because +the `Ordered` change below is breaking. -- ✅ **Milestone m1** (maintainer, 2026-11-04): it changes public API and - possibly lite-07 wire, so it lands before the cut. -- ✅ **The wire mechanism is this quest's call, with numbers** (maintainer, - 2026-11-04). Compare: - - **The publisher answers STOP_SENDING with SUBSCRIBE_DROP.** Lite already - sends SUBSCRIBE_DROP on the control stream when a group fails at the - publisher (`GroupServe::settle_failed`, `rs/moq-net/src/lite/publisher.rs`, - versions with a track stream), but a subscriber's STOP_SENDING doesn't - produce one. - - **The subscriber reads a group's header before it stops or evicts that - stream.** - - Doing both is fine if each is needed. The numbers come from the - receive-windows benchmark's overcommitted cells (256 streams, 4 MiB frames, - follow; `rs/moq-tokio/tests/integration/receive_credit.rs`), which - [moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) skips until - this lands: each must finish, with `delivered_frames` plus the reported - drops accounting for every group sent. Compare their throughput and the - control-stream bytes each mechanism adds. Start with the maintainer's question: - why does the subscriber stop or evict a stream before reading its header at - all? If receive-window eviction can wait for the header, the wire half may - shrink to that. Cover moq-transport too, or say why it differs. -- **Public drop signal.** Make the drop signal public in Rust. Choose its - shape here: a separate read named like the existing ones (for example - `recv_drop` returning the given-up run and its error), or a drop variant on - `recv_group`, the way container consumers already read `Frame | Gap | End`. - Prefer folding it into an existing read if that reads as naturally. The - ordered reader and resume keep using it internally. Its first consumer is - the receive-windows benchmark. Mirror it in `@moq/net` and the bindings only - for a named consumer (for example a player or container reader that skips - gaps), per the API audit rule that new - surface needs one; name it in the PR or leave the mirror out. -- **After the drop set.** This waited (2026-11-05) for Drop set, which - rewrote the lite-07 SUBSCRIBE_DROP wording and the drop signal, and - finished in [moq-dev/moq#8476](https://github.com/moq-dev/moq/pull/8476) on - 2026-11-12. `poll_drop` now takes no `Delivered` argument and yields the - given-up run with its `Hole` (`rs/moq-net/src/model/track.rs`, - `track/hole.rs`). Publish the API against that record. -- The drop set owns the per-cursor drop runs and their reasons. This quest - reports what a cursor gives up; it doesn't change how a cursor judges a - missing group. +- ✅ **Milestone** (maintainer, 2026-11-04): it changes public API, so it + lands before the cut. +- **After the drop set.** Drop set finished in + [moq-dev/moq#8476](https://github.com/moq-dev/moq/pull/8476) on 2026-11-12. + `poll_drop` now takes no `Delivered` argument and yields the given-up run + with its `Hole` (`rs/moq-net/src/model/track.rs`, `track/hole.rs`). Publish + the API against that record. The drop set owns the per-cursor drop runs and + their reasons; this reports what a cursor gives up. +- Mirror it in `@moq/net` and the bindings only for a named consumer (for + example a player or container reader that skips gaps), per the API audit + rule that new surface needs one; name it in the PR or leave the mirror out. -Decided 2026-11-07 (maintainer, /quest-plan from the API sweep of open PRs and remaining quests): ✅ key the drop signal by group start and land after +Decided 2026-11-07 (maintainer, /quest-plan from the API sweep of open PRs and +remaining quests): ✅ key the drop signal by group start and land after [time addressing's model](/quest/m2/time-addressing/model.md), so its public API never ships sequence-keyed (rejected: landing first and rekeying with the model). ✅ Drops surface as a `Gap { range, error }` item on `track::Ordered`, which already skips gaps through `poll_drop`, mirroring the container consumer's `Read::Gap` (`rs/moq-mux/src/container/consumer.rs`); `recv_group` is unchanged (rejected: a separate `recv_drop` read; a drop -variant on `recv_group`). Answer the maintainer's question above first: if -receive-window eviction can wait for the header, take the no-wire path, and -remove this quest from [lite07-finalize](/quest/m2/lite07-finalize.md)'s -Required. +variant on `recv_group`). Open, for whoever starts this, with the maintainer: a `Gap`'s start-keyed `range` doesn't say how many groups it covers once starts are sparse, yet @@ -91,11 +56,13 @@ Callers match the new item, and a caller that ignores drops takes the group arm; the PR's MIGRATE notes say so. `recv_group` and the unordered cursor are unchanged, so a reader that needs drop accounting reads through `Ordered`. `@moq/net` and the bindings mirror it only with a named consumer. -Wire: possibly lite-07 (SUBSCRIBE_DROP for a stopped group), decided here. +Wire: none; [the wire half](/quest/m2/group-drops-wire.md) owns it. ## Required - [Address groups by timestamp](/quest/m2/time-addressing/model.md) - the drop range is keyed by start +- [A moq-lite subscriber always learns which group it abandoned](/quest/m2/group-drops-wire.md) - the benchmark's cells finish only once no abandoned group is lost ## Related + - [The receive-windows benchmark](/quest/m3/receive-windows-evicted.md) - its overcommitted cells wait on this (skipped by [moq-dev/moq#7838](https://github.com/moq-dev/moq/pull/7838) until it lands) diff --git a/quest/m2/lite07-finalize.md b/quest/m2/lite07-finalize.md index 620da2d333d..c06a73c57fd 100644 --- a/quest/m2/lite07-finalize.md +++ b/quest/m2/lite07-finalize.md @@ -33,7 +33,9 @@ Chain, negotiated by its Setup Parameter, rides announcements until the lite-07 to lite-08 migration. Only [Routes and announces](/quest/m2/cluster-routes/README.md) gates the cut, not the later federation/P2P integrations. Decided 2026-10-13: routes now -owns the tier/partition correctness tests, so they run before the cut. Peer +owns the tier/partition correctness tests, so they run before the cut. +Reversed 2026-11-14 (the m2 triage, below): they moved to m3 with +[acceptance](/quest/m3/cluster-routing/acceptance.md). Peer grants and metadata-only subscriptions do not gate it: neither is clustering stability. Both are additive and, per the freeze policy, target whichever lite wip is current when they land. Decided 2026-10-25: no routing identity proof @@ -123,12 +125,36 @@ moq-net): ✅ the cut waits for the symbolic model of the Route Key Parameter routing invariant gating too, which sits behind the mesh model). The signed transcript freezes at the cut and a flaw in it can only be fixed on the wire. +Decided 2026-11-14 (the m2 triage before the cut, under /quest-afk, for the +maintainer's review), applying the maintainer's rule that m2 keeps only what +would need a breaking release had it landed right after the cut: + +- ✅ [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) and + [the request loop](/quest/m3/cluster-routing/request-loop.md) moved to m3 + and no longer gate this: both are tests and fixes with no wire change. + Accepted risk: a flaw they find in lite-07's route rules is fixed in + lite-08 or in local timers and configuration. Rejected: keeping them, so + the freeze waits on an L of tests. +- ✅ [The Playwright bump](/quest/m1/playwright-pin.md) moved to m1, so the + freeze no longer waits on nixpkgs. In its place, before the rename, run the + route key lane (`test/interop/clients/js/route-key.ts`) once with + Playwright 1.65.0 or later from npm, which bundles Chromium 158, and put + the result in the PR: the freeze still waits for Chromium to prove the + exporter the Route Key Parameter signs, as decided 2026-11-06, without + waiting for the pinned toolchain. If the tab fails, stop and report it, + since only the wire can fix the signed transcript. Rejected: dropping the + check; keeping the pin in m2. +- ✅ The wire half of group drops split out as + [its own quest](/quest/m2/group-drops-wire.md), which this waits on in + place of [the public drop signal](/quest/m2/group-drops.md), an API change + that doesn't touch the wire. + ## Required - [Routes and announces](/quest/m2/cluster-routes/README.md) - lite-07 carries the route layer: ROUTE per origin node and path-less ANNOUNCE, with the native hop list gone (only the temporary lite-06 compatibility chain remains) - [Lite-07 by start](/quest/m2/time-addressing/lite07.md) - lite-07 carries group starts, previous-start links, GROUP_END, and time bounds instead of sequence numbers - [@moq/net by start](/quest/m2/time-addressing/js.md) - JS speaks the same lite-07 wire -- [A group a subscriber gives up on is always reported](/quest/m2/group-drops.md) - may add SUBSCRIBE_DROP for a stopped group; leaves this list if it takes the no-wire path +- [A moq-lite subscriber always learns which group it abandoned](/quest/m2/group-drops-wire.md) - may add SUBSCRIBE_DROP for a stopped group; leaves this list if it takes the no-wire path ## Related diff --git a/quest/m2/time-addressing/bindings.md b/quest/m2/time-addressing/bindings.md index 3734a4ec2cf..ed74c753033 100644 --- a/quest/m2/time-addressing/bindings.md +++ b/quest/m2/time-addressing/bindings.md @@ -1,4 +1,4 @@ -# [M] Bindings address groups by start +# [S] Bindings address groups by start ## Goal @@ -17,6 +17,17 @@ arguments take a required one, and nothing is wall-clock stamped. A scale-less track's frames carry their group's key. See [the model](/quest/m2/time-addressing/model.md). +Resized from M to S 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): [moq-dev/moq#8638](https://github.com/moq-dev/moq/pull/8638) +already makes every binding's timestamps required and fills each group field +with the start, so what remains is the names. moq-ffi still says `sequence` +where it now means the start: the group record's field, `fetch_group`'s +argument, `seek`, and the docs on the ordered and arrival readers +(`rs/moq-ffi/src/consumer.rs`, `media.rs`). Rename them to `start` the same +way in moq-ffi, `moq-c`, and every binding, mirroring Rust's `group::Info`. +It stays in m2 because the rename is breaking and the cut would otherwise +publish a `sequence` that holds a start. + Public API: breaking in every binding. Wire: none. ## Required diff --git a/quest/m2/time-addressing/e2ee.md b/quest/m2/time-addressing/e2ee.md deleted file mode 100644 index 777c366993f..00000000000 --- a/quest/m2/time-addressing/e2ee.md +++ /dev/null @@ -1,21 +0,0 @@ -# [S] The E2EE nonce binds the group start - -## Goal - -The E2EE nonce binds a group's start timestamp instead of its sequence -number, in the draft and every implementation, so encrypted groups survive -the cut. - -## Plan - -Update `drafts/draft-lcurley-moq-e2ee.md`, `rs/moq-crypto`, and the JS side, -which has landed: `js/crypto/src/e2ee/derive.ts` builds `nonce(group, frame)` (about -line 156). The start is unique per track because starts strictly increase. -Run `just drafts check`. - -Public API: none. Wire: the E2EE nonce input changes. - -## Required - -- [Rust groups by start](/quest/m2/time-addressing/model.md) - the start the nonce binds -- [@moq/net by start](/quest/m2/time-addressing/js.md) - the JS start the JS half binds diff --git a/quest/m2/time-addressing/lite07.md b/quest/m2/time-addressing/lite07.md index 4ba853d5654..02e7786c968 100644 --- a/quest/m2/time-addressing/lite07.md +++ b/quest/m2/time-addressing/lite07.md @@ -48,6 +48,15 @@ Update `drafts/draft-lcurley-moq-lite.md` (fields, the group-end rules, and the lite-07 changelog) and `doc/concept/moq-lite.md`, and run `just drafts check` and `just test interop --all`. +Also reword `drafts/draft-lcurley-moq-e2ee.md`, which still calls the nonce's +group input a sequence (its group-allocation rule, about line 268): it is the +group's start, strictly increasing. The nonce bytes don't change, since both +the Rust and JS cores already feed it the group's wire ID, which +[the model](/quest/m2/time-addressing/model.md) makes the start. Folded in +2026-11-14 from the removed E2EE nonce quest (the m2 triage before the cut, +under /quest-afk, for the maintainer's review), since this PR's rename +outdates that wording. + Decided 2026-11-05 (maintainer, /quest-audit): ✅ this waits for Lite-07 FETCH is single-group only ([moq-dev/moq#8616](https://github.com/moq-dev/moq/pull/8616)), which rewrites the same lite-07 draft sections (`Range`, Positions, diff --git a/quest/m2/time-addressing/model.md b/quest/m2/time-addressing/model.md index 02065c0c8d9..704e010bed9 100644 --- a/quest/m2/time-addressing/model.md +++ b/quest/m2/time-addressing/model.md @@ -202,7 +202,7 @@ moq-transport-18, direct and through a relay, against a contiguous baseline Update `doc/concept`, the lite draft's legacy mapping, and the Rust half of every consumer the API change breaks to compile; -[consumers](/quest/m2/time-addressing/consumers.md) and +[consumers](/quest/m3/time-addressing-consumers.md) and [bindings](/quest/m2/time-addressing/bindings.md) own the behavior changes. Test the legacy mapping both ways on every wire, with the resume model (`rs/moq-net/src/model/resume_model.rs`, diff --git a/quest/m2/cluster-routes/acceptance.md b/quest/m3/cluster-routing/acceptance.md similarity index 89% rename from quest/m2/cluster-routes/acceptance.md rename to quest/m3/cluster-routing/acceptance.md index c938ceed927..7e4f4fc8af0 100644 --- a/quest/m2/cluster-routes/acceptance.md +++ b/quest/m3/cluster-routing/acceptance.md @@ -12,6 +12,18 @@ replace are retired. ## Plan +Moved from m2 to m3 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): ✅ m3, under the cluster-routing +epic, which waits for [Routes and announces](/quest/m2/cluster-routes/README.md) +(rejected: m2, where lite-07's freeze waits on an L of tests; m4 with other +tests, since the moq.pro lite-07 rollout waits on this proof). It is tests and +retired mitigations, with no wire or API change, so it can land after the cut +without a breaking release. It ranks right after m2, so it may still land +before the freeze. A flaw it finds in lite-07's route rules (item 30's +keep-alive, dispute-wheel, and return tests included) is fixed in lite-08, or +in the doubt timer and keep-alives, which are local. This reverses +lite07-finalize's 2026-10-13 rule that these tests run before the cut. + Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel): acceptance is of the path rule ([epic](/quest/m2/cluster-routes/README.md) Plan item 27), on the diff --git a/quest/m3/cluster-routing/federation.md b/quest/m3/cluster-routing/federation.md index d9239984dd7..59781713367 100644 --- a/quest/m3/cluster-routing/federation.md +++ b/quest/m3/cluster-routing/federation.md @@ -60,7 +60,7 @@ the same PR; the combined concept/setup guide follows separately. Decided 2026-11-06 (maintainer; the agent picked the children): require only the route children federation builds on, session integration (landed in [moq-dev/moq#8023](https://github.com/moq-dev/moq/pull/8023) and [moq-dev/moq#8293](https://github.com/moq-dev/moq/pull/8293)) and -[acceptance](/quest/m2/cluster-routes/acceptance.md), not the whole +[acceptance](/quest/m3/cluster-routing/acceptance.md), not the whole [route epic](/quest/m2/cluster-routes/README.md). Federation is relay-to-relay, so browser route-key proofs, the Playwright pin they wait on, and the mixed-version follow-up (mount takeover) gates the @@ -75,7 +75,7 @@ Rust/JS parity. Run `just check`, `just test interop --all`, and `just drafts ch ## Required -- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - the forwarding and partition fixtures this reuses, proven on the implementation +- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - the forwarding and partition fixtures this reuses, proven on the implementation ## Related diff --git a/quest/m2/cluster-routes/request-loop.md b/quest/m3/cluster-routing/request-loop.md similarity index 86% rename from quest/m2/cluster-routes/request-loop.md rename to quest/m3/cluster-routing/request-loop.md index 8dd0bff1fd1..6a0ffd99d27 100644 --- a/quest/m2/cluster-routes/request-loop.md +++ b/quest/m3/cluster-routing/request-loop.md @@ -13,6 +13,12 @@ no data and no failure. ## Plan +Moved from m2 to m3 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): ✅ m3, under the cluster-routing +epic (rejected: m2). A fixture and, if it hangs, a fix to where a relay's +pending request goes, with no wire field (the hop count was rejected below), +so it lands after the cut as a bug fix in shipped code. + Decided 2026-11-13 (maintainer, /quest-plan on the BGP failure modes): - ✅ A fixture on real relays, with no TLA+ (rejected: adding pending diff --git a/quest/m2/time-addressing/consumers.md b/quest/m3/time-addressing-consumers.md similarity index 50% rename from quest/m2/time-addressing/consumers.md rename to quest/m3/time-addressing-consumers.md index 1a604c5cbce..10b64ae556d 100644 --- a/quest/m2/time-addressing/consumers.md +++ b/quest/m3/time-addressing-consumers.md @@ -1,15 +1,30 @@ -# [L] Media consumers address groups by start +# [M] Media consumers address groups by start ## Goal -Every first-party consumer that numbered groups works by start timestamp, -in Rust and JS, and hang stops writing duration and discontinuity markers -that group ends and gaps now carry. The HLS/DASH export places each group on -the declared `media.join.interval` grid by its start instead of its first -frame's pts. +hang stops writing the duration and discontinuity markers that group ends +and gaps now carry, and the hang draft says so. Every first-party consumer +that numbered groups works by start timestamp, in Rust and JS, and the +HLS/DASH export places each group on the declared `media.join.interval` grid +by its start. ## Plan +Moved from m2 to m3 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): ✅ m3, since what remains breaks +nothing (rejected: m2; splitting a breaking part out, since none is left). +[The model](/quest/m2/time-addressing/model.md) +([moq-dev/moq#8638](https://github.com/moq-dev/moq/pull/8638)) converts the +Rust consumers whose API named group numbers: `moq fetch --group` and the +relay's `/fetch?group=` take a start, moq-mux `seek` and reads carry starts, +and moq-hls, moq-archive, and moq-transcode key by start. `@moq/hang`'s +`Read.group` keeps its name and carries whatever `@moq/net` keys by. Dropping +the markers is no break either: readers already tolerate their absence +(2026-10-25, below). What remains: the markers, the JS consumers' +continuity checks once [@moq/net by start](/quest/m2/time-addressing/js.md) +lands, the hang draft, and a pass over the list below for anything the model +left numbering groups. Resized from L to M with it. + Decided 2026-10-25 (maintainer), from the spike: - GROUP_END replaces hang's empty-frame duration marker @@ -36,11 +51,12 @@ relay and CLI `fetch --group`, and player continuity checks in the Rust and JS container consumers and `js/watch`. Update the hang draft and the docs each one makes stale; rename CLI flags per the repo's CLI rule. -Public API: breaking where a consumer exposes group numbers (CLI -`--group`, archive keys). Wire: hang drops empty duration frames and -discontinuity marker groups. +Public API: none left; the model renamed the CLI flag and archive keys. +Wire: hang drops empty duration frames and discontinuity marker groups, which +readers already tolerate. ## Required - [Rust groups by start](/quest/m2/time-addressing/model.md) - the Rust API these consume - [@moq/net by start](/quest/m2/time-addressing/js.md) - the JS API these consume +- [Lite-07 by start](/quest/m2/time-addressing/lite07.md) - GROUP_END carries the end the duration marker did diff --git a/quest/m4/cluster-fault-schedules.md b/quest/m4/cluster-fault-schedules.md index 98e43e8a5dc..e6b6209713f 100644 --- a/quest/m4/cluster-fault-schedules.md +++ b/quest/m4/cluster-fault-schedules.md @@ -50,4 +50,4 @@ Public API: none. Wire: none. ## Related - [Sim rule checks](/quest/m1/quic-sim-rules.md) - QUIC's rules checked on the same runs -- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - the scripted partition and failover fixtures +- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - the scripted partition and failover fixtures diff --git a/quest/m4/ietf-range-fetch.md b/quest/m4/ietf-range-fetch.md index 014dca828fb..fadbd3d2b23 100644 --- a/quest/m4/ietf-range-fetch.md +++ b/quest/m4/ietf-range-fetch.md @@ -30,7 +30,7 @@ frozen scope `doc/concept/standard.md` states, which kept only joining `FETCH`. What makes it possible: moq-transport's Prior Group ID Gap object extension, -which [IETF time addressing](/quest/m2/time-addressing/ietf.md) sends on +which [IETF time addressing](/quest/m4/ietf-time-addressing.md) sends on egress and reads on ingest as a best-effort SUBSCRIBE_SKIP. What counts as proven: @@ -71,7 +71,7 @@ Public API: none. Wire: none (draft-defined messages only). ## Required -- [IETF time addressing](/quest/m2/time-addressing/ietf.md) - reads Prior Group ID Gap on ingest +- [IETF time addressing](/quest/m4/ietf-time-addressing.md) - reads Prior Group ID Gap on ingest ## Closes diff --git a/quest/m2/time-addressing/ietf.md b/quest/m4/ietf-time-addressing.md similarity index 76% rename from quest/m2/time-addressing/ietf.md rename to quest/m4/ietf-time-addressing.md index 4f018b97431..f64b753e8d7 100644 --- a/quest/m2/time-addressing/ietf.md +++ b/quest/m4/ietf-time-addressing.md @@ -3,13 +3,23 @@ ## Goal moq-net keeps a moq-transport group ID verbatim as the group's key in both -directions. It sends each group's predecessor gap in Prior Group ID Gap as a +directions, as [the model](/quest/m2/time-addressing/model.md) builds it. It sends each group's predecessor gap in Prior Group ID Gap as a best-effort drop signal, and marks a whole group with END_OF_GROUP. It sends no Timestamp object property of its own. LOC object properties are proxied only between two moq-transport peers. ## Plan +Moved from m2 to m4 2026-11-14 (the m2 triage before the cut, under +/quest-afk, for the maintainer's review): ✅ m4 (rejected: m2; m3, where the +cut's re-split would keep a moq-transport wire change in the next cycle's +wire phase). The verbatim group ID, the only part this cut needs, rides +[the model](/quest/m2/time-addressing/model.md). What is left changes only +what moq-net sends third-party moq-transport peers, adds no public API, and +has no named consumer, and AGENTS.md ranks moq-transport compatibility below +moq-lite's. It sits beside the other moq-transport quests in m4, such as +[range FETCH](/quest/m4/ietf-range-fetch.md). + Decided 2026-11-03 (maintainer, the `/quest-import` grill of [moq-dev/moq#7573](https://github.com/moq-dev/moq/issues/7573)), replacing the 2026-10-25 plan that carried each object's PTS in TIMESTAMP (0x10) with diff --git a/quest/m5/e2ee/README.md b/quest/m5/e2ee/README.md index 3de4f4b064e..f7f8f96086b 100644 --- a/quest/m5/e2ee/README.md +++ b/quest/m5/e2ee/README.md @@ -23,7 +23,7 @@ The contract is [draft-lcurley-moq-e2ee](/drafts/draft-lcurley-moq-e2ee.md), pro - An encrypting publisher refuses a shared or explicit epoch (maintainer, 2026-10-08). Two producers handed one epoch would derive the same keys and repeat every nonce. Both cores produce only under an epoch they minted themselves; consuming still binds a discovered one. Rejected: a per-instance salt. State the rule in the draft's epoch section. - The epoch is untrusted and unauthenticated. A wrong epoch fails authentication and a withheld one denies service; neither can make a nonce repeat, because only the publisher instance chooses what it encrypts under. This is the same trust a cache needs to serve the right instance. First-party plaintext publishers already mint the same route epoch. - Nothing in the path says the bytes are encrypted. The format after decryption (`meeting.hang`) is inside the opaque name; a plaintext player, exporter, or matcher that opens a protected broadcast finds no catalog it can read and fails with its usual typed refusal, the same as for any format it does not support. -- One 32-byte secret authorizes the whole broadcast; HKDF-SHA-256 derives separate AES-128-GCM keys for each physical track and for grouped-frame versus datagram domains. A grouped frame uses a 96-bit nonce of a 64-bit group identity and `uint32_be(frame)`. The group identity becomes the group's start timestamp, not its sequence, once [the E2EE nonce binds the group start](/quest/m2/time-addressing/e2ee.md) lands; until then the draft and both cores use `uint64_be(group)`. A datagram uses its sequence with frame zero under the datagram domain. Empty AAD: every immutable end-to-end field is in the HKDF info or the nonce. +- One 32-byte secret authorizes the whole broadcast; HKDF-SHA-256 derives separate AES-128-GCM keys for each physical track and for grouped-frame versus datagram domains. A grouped frame uses a 96-bit nonce of a 64-bit group identity and `uint32_be(frame)`. `group` is the group's wire ID, which is its start once [the model](/quest/m2/time-addressing/model.md) keys groups by start, so the nonce input needs no change; [lite-07 by start](/quest/m2/time-addressing/lite07.md) updates the draft's wording. A datagram uses its sequence with frame zero under the datagram domain. Empty AAD: every immutable end-to-end field is in the HKDF info or the nonce. - Within an instance, group and datagram sequences are allocated monotonically and frames are numbered in write order, which is the whole reuse rule. There is no ciphertext retention or retransmission API: relays forward bytes unchanged, and an application that needs to resend encrypts nothing twice because it never gets the same identity twice. - Per-key limits are `2^24` AEAD invocations (failed opens included) and `2^36` plaintext bytes. The generation handle owns each key's accounting, shared by every track and subscription through it and never evicted while the application holds it; binding the epoch again starts fresh, since remembering retired epochs would be state a relay grows (maintainer, 2026-10-24). Rejected: a credential-level registry of live generations, and refusing to re-bind a released epoch. Datagram plaintext is capped at `1200 - 24 - 16` bytes against the widest moq-lite header; a publisher cannot see the Subscribe ID each hop encodes, so the library does not pretend to budget it. diff --git a/quest/m5/routes-browser-proof.md b/quest/m5/routes-browser-proof.md index 1fca454aec1..ef5f9d4b532 100644 --- a/quest/m5/routes-browser-proof.md +++ b/quest/m5/routes-browser-proof.md @@ -12,7 +12,7 @@ the relay's log for the tab's verified proof. Each build either must prove or must send no proof. One that must send none either holds the lite-07 cut, skipping or failing under `CI_STRICT` (which release PRs set), or connects unproven by design and passes. Chromium 158 and later must prove, which the -[Playwright bump](/quest/m2/cluster-routes/playwright-pin.md) +[Playwright bump](/quest/m1/playwright-pin.md) reaches. Every Firefox build connects unproven, so the lite-07 cut does not wait on Firefox. @@ -55,7 +55,7 @@ Once a Firefox release carries neqo's fix, gate `route_key.ts` on Firefox majors before it, set the lane's table (`uncovered` in `route-key.ts`) to require a proof from it on and to pass older majors unproven, and bump Playwright to a release bundling it, the way the -[Playwright bump](/quest/m2/cluster-routes/playwright-pin.md) does for +[Playwright bump](/quest/m1/playwright-pin.md) does for Chromium. Verify the fixed build against the relay the way the 2026-11-06 check did: its export must match the relay's for the same session. From c6392240a77ca3e9035d1a8e536394c4eee84be3 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 14 Nov 2026 12:32:30 -0800 Subject: [PATCH 2/3] quest: record the maintainer's picks; route acceptance stays in m2 The maintainer kept route acceptance in the m2 routes epic, gating the cut per the 2026-10-13 rule, and kept the route stream and interest set in m2. Move acceptance back and record both picks in the affected Plans. Co-Authored-By: Claude Opus 5.5 --- quest/m2/README.md | 19 ++++++++++------- quest/m2/cluster-routes/README.md | 6 +++--- .../cluster-routes}/acceptance.md | 17 ++++++--------- quest/m2/cluster-routes/interest-set.md | 7 +++++++ quest/m2/cluster-routes/route-stream.md | 7 +++++++ quest/m2/cluster-routes/switch.md | 2 +- quest/m2/lite07-finalize.md | 21 ++++++++++--------- quest/m3/cluster-routing/federation.md | 4 ++-- quest/m4/cluster-fault-schedules.md | 2 +- 9 files changed, 49 insertions(+), 36 deletions(-) rename quest/{m3/cluster-routing => m2/cluster-routes}/acceptance.md (89%) diff --git a/quest/m2/README.md b/quest/m2/README.md index cd6699fe775..25aeef3c9ab 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -218,14 +218,13 @@ rule here). Its lag rule reshapes `main`-only API the cut would publish (the cut should not ship the 2026-11-09 stretch model, which lets audio trail video by up to 2 s. -Decided 2026-11-14 (m2 triage before the cut, under /quest-afk, for the -maintainer's review; the maintainer asked that what remains be unblocked or -punted). m2 keeps only what would need a breaking release had it landed right -after the cut: - -- ✅ Left m2: [route acceptance](/quest/m3/cluster-routing/acceptance.md) - and [the request loop](/quest/m3/cluster-routing/request-loop.md) to m3's - cluster-routing epic (tests and fixes, no wire); +Decided 2026-11-14 (m2 triage before the cut, under /quest-afk; the +maintainer asked that what remains be unblocked or punted, and picked these on +[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768)). m2 keeps only +what would need a breaking release had it landed right after the cut: + +- ✅ Left m2: [the request loop](/quest/m3/cluster-routing/request-loop.md) + to m3's cluster-routing epic (a fixture and a fix, no wire); [media consumers](/quest/m3/time-addressing-consumers.md) to m3 (its API breaks ride the model; dropping hang's markers is tolerated by readers); [moq-transport time addressing](/quest/m4/ietf-time-addressing.md) to m4 @@ -242,6 +241,10 @@ after the cut: router key per announce stream, which the route model doesn't check, and keep the reopen-and-hand-over machinery for its lifetime (rejected: moving both to lite-08). +- ✅ [Route acceptance](/quest/m2/cluster-routes/acceptance.md) stays in + the routes epic and gates the cut, per the 2026-10-13 rule that routes' + tier and partition tests run before it (maintainer; rejected: moving it to + m3 and fixing late routing flaws in lite-08). - ✅ [Group drops](/quest/m2/group-drops.md) split: its lite-07 wire question is [its own quest](/quest/m2/group-drops-wire.md), which starts now and gates the freeze; the public `Ordered` API waits for the model. diff --git a/quest/m2/cluster-routes/README.md b/quest/m2/cluster-routes/README.md index 69f8607797d..4f9c28e3070 100644 --- a/quest/m2/cluster-routes/README.md +++ b/quest/m2/cluster-routes/README.md @@ -57,11 +57,11 @@ The items below were decided 2026-11-10 (maintainer, /quest-plan on lite-07 rout Measured on 24 relays (the mesh sweep's sparse shape, 16 seeds), against today's router, with the doubt lasting 4 hops of delay: a detour settles in 12 hops of delay where the distance takes 15.7, and in 6.2 where it does not run through the far end of the closed link; the publisher's relay dying costs 124 route messages where the distance costs 276, with no loop and 6 claims sent again; and a link closing in a clique costs 44 messages with one publisher behind it and 198 with eight, where the distance costs 621 and 5,024. Accepted: a detour through the far end of a closed link waits the timer out; selected routes can loop for a moment when two unrelated things fail at once (32 of 120,000 churn steps), which the distance never does; and holds and doubt have passed sweeps. The model covers both, but its no-stale-route property holds only for one failure and a patient timer; `StaleIsChased` bounds the rest. The timer's length is the model's and the router's to settle, from the maintainer's 1 s. Rejected: Babel's distance; paths with nothing else, which hunt through stale paths (65,219 messages for one publisher leaving a clique of 12); no doubt, which loops when a relay with several neighbours dies; and a doubt lifted by an epoch the node floods, which resolves in a couple of hops but costs a message per session on each relay-to-relay close ("Epoches are a bit scary in terms of messages"). -28. ✅ Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel), asked how item 27's removal is split and ordered: **the router first with no wire change, then a switch of the sessions, and the switch lands before the route stream.** [The router](https://github.com/moq-dev/moq/pull/8622) runs the path rule with a route per scope, sans-IO, beside today's router. [The switch](/quest/m2/cluster-routes/switch.md) puts it on the lite-07-wip wire, the draft, the Rust sessions, and `js/net`, and deletes Babel's router. [The interest set](/quest/m2/cluster-routes/interest-set.md) then edits the path router only, and [the route stream](/quest/m2/cluster-routes/route-stream.md) follows the switch with no echo or route request to carry. The switch's recommended wire puts the answer that ends a hold on the publisher half, behind the routes its sender sent first, so the path rule needs no order between streams that today's sessions lack for one prefix. [Acceptance](/quest/m3/cluster-routing/acceptance.md) is of the switched sessions, and the inductive invariant stays in m1, rewritten for the path, without `LoopFree` as an invariant. Rejected: the router quest in m1; one quest for router, wire, draft, sessions, and `js/net`; the route stream first, which builds the echo and ROUTE_REQUEST on the new stream and then deletes them; one wire change for the path rule and the one stream together; moving the inductive invariant to m4; deleting it. Reversed 2026-11-13 (maintainer, /quest-complete): ✅ the inductive invariant is deleted, since Apalache cannot step even one transition of the route model ([moq-dev/moq#8564](https://github.com/moq-dev/moq/pull/8564)), no Rust TLA+ checker qualifies ([moq-dev/moq#8600](https://github.com/moq-dev/moq/pull/8600), [moq-dev/moq#8669](https://github.com/moq-dev/moq/pull/8669)), and no more JVM model checking is wanted here (rejected: keeping it paused). +28. ✅ Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel), asked how item 27's removal is split and ordered: **the router first with no wire change, then a switch of the sessions, and the switch lands before the route stream.** [The router](https://github.com/moq-dev/moq/pull/8622) runs the path rule with a route per scope, sans-IO, beside today's router. [The switch](/quest/m2/cluster-routes/switch.md) puts it on the lite-07-wip wire, the draft, the Rust sessions, and `js/net`, and deletes Babel's router. [The interest set](/quest/m2/cluster-routes/interest-set.md) then edits the path router only, and [the route stream](/quest/m2/cluster-routes/route-stream.md) follows the switch with no echo or route request to carry. The switch's recommended wire puts the answer that ends a hold on the publisher half, behind the routes its sender sent first, so the path rule needs no order between streams that today's sessions lack for one prefix. [Acceptance](/quest/m2/cluster-routes/acceptance.md) is of the switched sessions, and the inductive invariant stays in m1, rewritten for the path, without `LoopFree` as an invariant. Rejected: the router quest in m1; one quest for router, wire, draft, sessions, and `js/net`; the route stream first, which builds the echo and ROUTE_REQUEST on the new stream and then deletes them; one wire change for the path rule and the one stream together; moving the inductive invariant to m4; deleting it. Reversed 2026-11-13 (maintainer, /quest-complete): ✅ the inductive invariant is deleted, since Apalache cannot step even one transition of the route model ([moq-dev/moq#8564](https://github.com/moq-dev/moq/pull/8564)), no Rust TLA+ checker qualifies ([moq-dev/moq#8600](https://github.com/moq-dev/moq/pull/8600), [moq-dev/moq#8669](https://github.com/moq-dev/moq/pull/8669)), and no more JVM model checking is wanted here (rejected: keeping it paused). -29. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), asked how the path rule keeps the `upstream` guarantee, which the prototype left out and [the switch](/quest/m2/cluster-routes/switch.md) had listed for removal with Babel's machinery: **a route keeps one sticky down-only flag beside its path.** A relay sets it on a route it learns over a link marked `upstream`, it is never cleared on a later hop, and a relay never sends a flagged route over an upstream link. The flag is export policy, not loop avoidance, so the path does not replace it: a relay that hears a CDN route from a LAN peer learned it on a link that is not upstream, and only the flag tells it the route came down from an upstream. That case is a local cluster with more than one uplink ([outbound federation](/quest/m3/cluster-routing/federation.md)), where a relay whose own uplink died reaches the CDN through a peer; an edge that dials only its cores needs just the local rule. This is the Only-To-Customer attribute of BGP roles (RFC 9234). The router (`rs/moq-net/src/route/path.rs`, built in [#8622](https://github.com/moq-dev/moq/pull/8622)) carries the flag and its export check, [the switch](/quest/m2/cluster-routes/switch.md) adds them to `RouteHandoff.tla` and keeps the flag on ROUTE_START and ROUTE_UPDATE, and [acceptance](/quest/m3/cluster-routing/acceptance.md)'s two-uplink mesh proves it. Sender side only, as today. Rejected: a mark on each hop of the path, which gives the same answer from more bytes and model state; the local rule with no flag, which either leaks through a LAN peer or gives up the dead-uplink fallback; also refusing a flagged route that arrives from a link whose grant marks the sender as a customer, which can be added later without a wire change. +29. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), asked how the path rule keeps the `upstream` guarantee, which the prototype left out and [the switch](/quest/m2/cluster-routes/switch.md) had listed for removal with Babel's machinery: **a route keeps one sticky down-only flag beside its path.** A relay sets it on a route it learns over a link marked `upstream`, it is never cleared on a later hop, and a relay never sends a flagged route over an upstream link. The flag is export policy, not loop avoidance, so the path does not replace it: a relay that hears a CDN route from a LAN peer learned it on a link that is not upstream, and only the flag tells it the route came down from an upstream. That case is a local cluster with more than one uplink ([outbound federation](/quest/m3/cluster-routing/federation.md)), where a relay whose own uplink died reaches the CDN through a peer; an edge that dials only its cores needs just the local rule. This is the Only-To-Customer attribute of BGP roles (RFC 9234). The router (`rs/moq-net/src/route/path.rs`, built in [#8622](https://github.com/moq-dev/moq/pull/8622)) carries the flag and its export check, [the switch](/quest/m2/cluster-routes/switch.md) adds them to `RouteHandoff.tla` and keeps the flag on ROUTE_START and ROUTE_UPDATE, and [acceptance](/quest/m2/cluster-routes/acceptance.md)'s two-uplink mesh proves it. Sender side only, as today. Rejected: a mark on each hop of the path, which gives the same answer from more bytes and model state; the local rule with no flag, which either leaks through a LAN peer or gives up the dead-uplink fallback; also refusing a flagged route that arrives from a link whose grant marks the sender as a customer, which can be added later without a wire change. -30. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), after a survey of BGP, EIGRP, and their successors against item 27: most of the path rule already matches that prior art (AS_PATH loop detection, root-cause withdrawal, graceful restart, End-of-RIB, outbound route filtering, and item 29's Only-To-Customer flag). Three gaps are taken, all in [the switch](/quest/m2/cluster-routes/switch.md) and [acceptance](/quest/m3/cluster-routing/acceptance.md): **a dead-hop message on a scoped session applies only to the routes heard on that session and casts no doubt**, since in BGP a neighbour withdraws only what it sent, and a scoped peer (a federated relay, later a browser) could otherwise name a core hop it only read in a path and drop healthy routes outside its scope; **holds are bounded in time**, a neighbour's missing answer counting as nothing after a deadline, and a session whose announce stream has stopped draining is closed, which avoids EIGRP's stuck-in-active and BGP's zombie routes (RFC 9687), and is safe because a hold protects presence, not loop freedom; and **three tests before any design change**: neighbours noticing a dead relay up to the 3 s keep-alive apart (to size the doubt timer, measured in hops of delay today), a three-relay priority dispute wheel (RFC 4264's wedgies, since priority ranks above cost), and a primary that fails and returns. No wire bytes change; the first defines what the dead-hop message means. Rejected: declaring the link relation in SETUP and refusing leaked routes on receipt (RFC 9234), since the accepting side already knows the relation from its grant and it adds wire for a misconfiguration; MRAI and route-flap damping, which exist because BGP delays announcements; link state; per-hop signatures. +30. ✅ Decided 2026-11-12 (maintainer, /quest-audit before the cut), after a survey of BGP, EIGRP, and their successors against item 27: most of the path rule already matches that prior art (AS_PATH loop detection, root-cause withdrawal, graceful restart, End-of-RIB, outbound route filtering, and item 29's Only-To-Customer flag). Three gaps are taken, all in [the switch](/quest/m2/cluster-routes/switch.md) and [acceptance](/quest/m2/cluster-routes/acceptance.md): **a dead-hop message on a scoped session applies only to the routes heard on that session and casts no doubt**, since in BGP a neighbour withdraws only what it sent, and a scoped peer (a federated relay, later a browser) could otherwise name a core hop it only read in a path and drop healthy routes outside its scope; **holds are bounded in time**, a neighbour's missing answer counting as nothing after a deadline, and a session whose announce stream has stopped draining is closed, which avoids EIGRP's stuck-in-active and BGP's zombie routes (RFC 9687), and is safe because a hold protects presence, not loop freedom; and **three tests before any design change**: neighbours noticing a dead relay up to the 3 s keep-alive apart (to size the doubt timer, measured in hops of delay today), a three-relay priority dispute wheel (RFC 4264's wedgies, since priority ranks above cost), and a primary that fails and returns. No wire bytes change; the first defines what the dead-hop message means. Rejected: declaring the link relation in SETUP and refusing leaked routes on receipt (RFC 9234), since the accepting side already knows the relation from its grant and it adds wire for a misconfiguration; MRAI and route-flap damping, which exist because BGP delays announcements; link state; per-hop signatures. The route layer's core landed in [moq-dev/moq#7676](https://github.com/moq-dev/moq/pull/7676): a diff --git a/quest/m3/cluster-routing/acceptance.md b/quest/m2/cluster-routes/acceptance.md similarity index 89% rename from quest/m3/cluster-routing/acceptance.md rename to quest/m2/cluster-routes/acceptance.md index 7e4f4fc8af0..9460a5e4c5c 100644 --- a/quest/m3/cluster-routing/acceptance.md +++ b/quest/m2/cluster-routes/acceptance.md @@ -12,17 +12,12 @@ replace are retired. ## Plan -Moved from m2 to m3 2026-11-14 (the m2 triage before the cut, under -/quest-afk, for the maintainer's review): ✅ m3, under the cluster-routing -epic, which waits for [Routes and announces](/quest/m2/cluster-routes/README.md) -(rejected: m2, where lite-07's freeze waits on an L of tests; m4 with other -tests, since the moq.pro lite-07 rollout waits on this proof). It is tests and -retired mitigations, with no wire or API change, so it can land after the cut -without a breaking release. It ranks right after m2, so it may still land -before the freeze. A flaw it finds in lite-07's route rules (item 30's -keep-alive, dispute-wheel, and return tests included) is fixed in lite-08, or -in the doubt timer and keep-alives, which are local. This reverses -lite07-finalize's 2026-10-13 rule that these tests run before the cut. +Decided 2026-11-14 (maintainer, /quest-complete on +[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768)): ✅ stays in +m2 and gates the cut, per lite07-finalize's 2026-10-13 rule that routes' +tier and partition tests run before the cut (rejected: moving it to m3 and +fixing late routing flaws in lite-08). A flaw found here is fixed on +lite-07-wip before it freezes. Decided 2026-11-12 (maintainer, /quest-plan on the quests still written for Babel): acceptance is of the path rule diff --git a/quest/m2/cluster-routes/interest-set.md b/quest/m2/cluster-routes/interest-set.md index 5ecc2b01bdd..7e0cadad8eb 100644 --- a/quest/m2/cluster-routes/interest-set.md +++ b/quest/m2/cluster-routes/interest-set.md @@ -15,6 +15,13 @@ carries it. ## Plan +Decided 2026-11-14 (maintainer, /quest-complete on +[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768), the m2 triage +before the cut): ✅ stays in m2 (rejected: moving the route stream and the +interest set to lite-08). It changes no wire or API on its own, but +[the route stream](/quest/m2/cluster-routes/route-stream.md) needs it, and +no quest requires one in a later milestone. + Decided 2026-11-10 (maintainer, /quest-plan on lite-07 routing). The model goes first because the set's edit rule is the one new rule in this redesign, and every earlier routing bug was an ordering nobody had enumerated. diff --git a/quest/m2/cluster-routes/route-stream.md b/quest/m2/cluster-routes/route-stream.md index 36ba89e3311..f863eabee54 100644 --- a/quest/m2/cluster-routes/route-stream.md +++ b/quest/m2/cluster-routes/route-stream.md @@ -14,6 +14,13 @@ and lite-06 and older and moq-transport are untouched. ## Plan +Decided 2026-11-14 (maintainer, /quest-complete on +[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768), the m2 triage +before the cut): ✅ stays in m2, gating lite-07's freeze (rejected: moving the route stream and the +interest set to lite-08). Without it lite-07 would freeze with one router key per announce +stream, which the route model doesn't check, and keep the reopen-and-hand-over +machinery for its lifetime. + Decided 2026-11-10 (maintainer, /quest-plan on lite-07 routing). Why: today a side's requests ride the streams it opened and its answers ride diff --git a/quest/m2/cluster-routes/switch.md b/quest/m2/cluster-routes/switch.md index a3d35a641e0..4cc9ed91e02 100644 --- a/quest/m2/cluster-routes/switch.md +++ b/quest/m2/cluster-routes/switch.md @@ -168,4 +168,4 @@ Public API: none expected. Wire: lite-07-wip only. ## Related - [Each side says everything about routing on one stream](/quest/m2/cluster-routes/route-stream.md) - moves these messages onto one stream per side afterwards -- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - proves the switched sessions end to end +- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - proves the switched sessions end to end diff --git a/quest/m2/lite07-finalize.md b/quest/m2/lite07-finalize.md index c06a73c57fd..f29516369b3 100644 --- a/quest/m2/lite07-finalize.md +++ b/quest/m2/lite07-finalize.md @@ -34,8 +34,7 @@ to lite-08 migration. Only [Routes and announces](/quest/m2/cluster-routes/README.md) gates the cut, not the later federation/P2P integrations. Decided 2026-10-13: routes now owns the tier/partition correctness tests, so they run before the cut. -Reversed 2026-11-14 (the m2 triage, below): they moved to m3 with -[acceptance](/quest/m3/cluster-routing/acceptance.md). Peer +Reaffirmed 2026-11-14 (maintainer, the m2 triage, below). Peer grants and metadata-only subscriptions do not gate it: neither is clustering stability. Both are additive and, per the freeze policy, target whichever lite wip is current when they land. Decided 2026-10-25: no routing identity proof @@ -125,16 +124,18 @@ moq-net): ✅ the cut waits for the symbolic model of the Route Key Parameter routing invariant gating too, which sits behind the mesh model). The signed transcript freezes at the cut and a flaw in it can only be fixed on the wire. -Decided 2026-11-14 (the m2 triage before the cut, under /quest-afk, for the -maintainer's review), applying the maintainer's rule that m2 keeps only what +Decided 2026-11-14 (the m2 triage before the cut, under /quest-afk; the +maintainer picked these on +[moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768)), applying the maintainer's rule that m2 keeps only what would need a breaking release had it landed right after the cut: -- ✅ [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) and - [the request loop](/quest/m3/cluster-routing/request-loop.md) moved to m3 - and no longer gate this: both are tests and fixes with no wire change. - Accepted risk: a flaw they find in lite-07's route rules is fixed in - lite-08 or in local timers and configuration. Rejected: keeping them, so - the freeze waits on an L of tests. +- ✅ [The request loop](/quest/m3/cluster-routing/request-loop.md) moved + to m3 and no longer gates this: a fixture and a fix with no wire change. +- ✅ [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) stays + in [Routes and announces](/quest/m2/cluster-routes/README.md), so this + still waits on it (maintainer, /quest-complete on + [moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768); rejected: + moving it to m3 and fixing late routing flaws in lite-08). - ✅ [The Playwright bump](/quest/m1/playwright-pin.md) moved to m1, so the freeze no longer waits on nixpkgs. In its place, before the rename, run the route key lane (`test/interop/clients/js/route-key.ts`) once with diff --git a/quest/m3/cluster-routing/federation.md b/quest/m3/cluster-routing/federation.md index 59781713367..d9239984dd7 100644 --- a/quest/m3/cluster-routing/federation.md +++ b/quest/m3/cluster-routing/federation.md @@ -60,7 +60,7 @@ the same PR; the combined concept/setup guide follows separately. Decided 2026-11-06 (maintainer; the agent picked the children): require only the route children federation builds on, session integration (landed in [moq-dev/moq#8023](https://github.com/moq-dev/moq/pull/8023) and [moq-dev/moq#8293](https://github.com/moq-dev/moq/pull/8293)) and -[acceptance](/quest/m3/cluster-routing/acceptance.md), not the whole +[acceptance](/quest/m2/cluster-routes/acceptance.md), not the whole [route epic](/quest/m2/cluster-routes/README.md). Federation is relay-to-relay, so browser route-key proofs, the Playwright pin they wait on, and the mixed-version follow-up (mount takeover) gates the @@ -75,7 +75,7 @@ Rust/JS parity. Run `just check`, `just test interop --all`, and `just drafts ch ## Required -- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - the forwarding and partition fixtures this reuses, proven on the implementation +- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - the forwarding and partition fixtures this reuses, proven on the implementation ## Related diff --git a/quest/m4/cluster-fault-schedules.md b/quest/m4/cluster-fault-schedules.md index e6b6209713f..98e43e8a5dc 100644 --- a/quest/m4/cluster-fault-schedules.md +++ b/quest/m4/cluster-fault-schedules.md @@ -50,4 +50,4 @@ Public API: none. Wire: none. ## Related - [Sim rule checks](/quest/m1/quic-sim-rules.md) - QUIC's rules checked on the same runs -- [Route layer acceptance](/quest/m3/cluster-routing/acceptance.md) - the scripted partition and failover fixtures +- [Route layer acceptance](/quest/m2/cluster-routes/acceptance.md) - the scripted partition and failover fixtures From ba30d08f05d42fd020850056e85d45eea307628a Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 14 Nov 2026 12:41:33 -0800 Subject: [PATCH 3/3] quest: the release cut waits on the Playwright pin; consumers keep --group The cut PR's interop lane runs with CI_STRICT, which fails the route key lane on a Chromium below 158, so the release cut requires the m1 pin and lite07-finalize's manual Chromium 158 run is only an early signal. The model keeps `moq fetch --group`, so the consumers quest renames no flag. Co-Authored-By: Claude Opus 5.5 --- quest/m1/playwright-pin.md | 9 ++++++--- quest/m2/README.md | 5 +++-- quest/m2/lite07-finalize.md | 20 +++++++++++--------- quest/m3/release/cut.md | 1 + quest/m3/time-addressing-consumers.md | 9 ++++++--- 5 files changed, 27 insertions(+), 17 deletions(-) diff --git a/quest/m1/playwright-pin.md b/quest/m1/playwright-pin.md index 66342e444c0..13caccd8974 100644 --- a/quest/m1/playwright-pin.md +++ b/quest/m1/playwright-pin.md @@ -25,9 +25,12 @@ Moved from m2 to m1 2026-11-14 (the m2 triage before the cut, under /quest-afk, for the maintainer's review): ✅ m1, since a toolchain bump breaks nothing and builds on no m2 work (rejected: m2, where the cut waited on nixpkgs; m4 or m5, which hold it behind the cut or the next wire cut once -nixpkgs lands). This replaces the 2026-11-06 decision below that the lite-07 -cut waits for the bump: [lite07-finalize](/quest/m2/lite07-finalize.md) -instead runs the lane once with npm's Playwright 1.65.0 before the rename. +nixpkgs lands). [The release cut](/quest/m3/release/cut.md) requires it in +place of lite07-finalize, since the cut PR's interop lane runs with +`CI_STRICT` and fails the route key lane on a Chromium below 158; +[lite07-finalize](/quest/m2/lite07-finalize.md) runs the lane once with +npm's Playwright 1.65.0 before the rename as an early signal. This amends +the 2026-11-06 decision below that the lite-07 cut waits for the bump. Decided 2026-11-06 (maintainer, /quest-complete, on Pullfrog's review of [moq-dev/moq#8037](https://github.com/moq-dev/moq/pull/8037)): ✅ bump diff --git a/quest/m2/README.md b/quest/m2/README.md index 25aeef3c9ab..7dacc66f1af 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -229,8 +229,9 @@ what would need a breaking release had it landed right after the cut: breaks ride the model; dropping hang's markers is tolerated by readers); [moq-transport time addressing](/quest/m4/ietf-time-addressing.md) to m4 (low-priority compatibility, no named consumer); and the - [Playwright bump](/quest/m1/playwright-pin.md) to m1, with - lite07-finalize checking Chromium 158 once by hand instead. The E2EE nonce + [Playwright bump](/quest/m1/playwright-pin.md) to m1, which the release + cut requires in place of lite07-finalize (its strict interop lane needs + Chromium 158), with lite07-finalize checking Chromium 158 once by hand. The E2EE nonce quest was removed: the nonce already binds the wire ID, which becomes the start, and lite-07 by start rewords the draft. Rejected for each: staying in m2. diff --git a/quest/m2/lite07-finalize.md b/quest/m2/lite07-finalize.md index f29516369b3..f10cc5eb5ef 100644 --- a/quest/m2/lite07-finalize.md +++ b/quest/m2/lite07-finalize.md @@ -136,15 +136,17 @@ would need a breaking release had it landed right after the cut: still waits on it (maintainer, /quest-complete on [moq-dev/moq#8768](https://github.com/moq-dev/moq/pull/8768); rejected: moving it to m3 and fixing late routing flaws in lite-08). -- ✅ [The Playwright bump](/quest/m1/playwright-pin.md) moved to m1, so the - freeze no longer waits on nixpkgs. In its place, before the rename, run the - route key lane (`test/interop/clients/js/route-key.ts`) once with - Playwright 1.65.0 or later from npm, which bundles Chromium 158, and put - the result in the PR: the freeze still waits for Chromium to prove the - exporter the Route Key Parameter signs, as decided 2026-11-06, without - waiting for the pinned toolchain. If the tab fails, stop and report it, - since only the wire can fix the signed transcript. Rejected: dropping the - check; keeping the pin in m2. +- ✅ [The Playwright bump](/quest/m1/playwright-pin.md) moved to m1 and + gates [the release cut](/quest/m3/release/cut.md) instead of this: the cut + PR's interop lane runs with `CI_STRICT` (`.github/workflows/interop.yml`), + which fails the route key lane on a Chromium below 158, so only the pinned + toolchain clears it. As an early signal, before the rename, run the route + key lane (`test/interop/clients/js/route-key.ts`) once with Playwright + 1.65.0 or later from npm, which bundles Chromium 158, and put the result in + the PR. If the tab fails, stop and report it, since only the wire can fix + the signed transcript. Rejected: keeping the pin in m2, where the freeze + waits on nixpkgs as well as the cut; dropping the check, which would find a + transcript flaw only after the freeze. - ✅ The wire half of group drops split out as [its own quest](/quest/m2/group-drops-wire.md), which this waits on in place of [the public drop signal](/quest/m2/group-drops.md), an API change diff --git a/quest/m3/release/cut.md b/quest/m3/release/cut.md index d81a6c49a82..77d647e0853 100644 --- a/quest/m3/release/cut.md +++ b/quest/m3/release/cut.md @@ -214,3 +214,4 @@ with the suites above. - [Interop and Video pass on main](/quest/m0/interop-green/README.md) - the cut PR's release gate runs `interop.yml`, which failed on `main` every day through 2026-11-12 - [Nightly passes on main](/quest/m0/nightly/README.md) - the release gate runs `features.yml`, red in the 2026-11-12 Nightly - [Claim new npm names](/quest/m3/release/npm-first-publish.md) - trusted publishing can publish every new `@moq/*` package +- [The Playwright bump](/quest/m1/playwright-pin.md) - the cut PR's interop lane runs with `CI_STRICT`, which fails the route key lane on a Chromium below 158 diff --git a/quest/m3/time-addressing-consumers.md b/quest/m3/time-addressing-consumers.md index 10b64ae556d..33f49946753 100644 --- a/quest/m3/time-addressing-consumers.md +++ b/quest/m3/time-addressing-consumers.md @@ -16,7 +16,7 @@ nothing (rejected: m2; splitting a breaking part out, since none is left). [The model](/quest/m2/time-addressing/model.md) ([moq-dev/moq#8638](https://github.com/moq-dev/moq/pull/8638)) converts the Rust consumers whose API named group numbers: `moq fetch --group` and the -relay's `/fetch?group=` take a start, moq-mux `seek` and reads carry starts, +relay's `/fetch?group=` keep their names and take a start, moq-mux `seek` and reads carry starts, and moq-hls, moq-archive, and moq-transcode key by start. `@moq/hang`'s `Read.group` keeps its name and carries whatever `@moq/net` keys by. Dropping the markers is no break either: readers already tolerate their absence @@ -49,9 +49,12 @@ HLS/DASH export, `seek` for GOP-aligned failover in moq-mux, HLS import's discontinuity packing, transcode's 1:1 numbering, archive keys and resume, relay and CLI `fetch --group`, and player continuity checks in the Rust and JS container consumers and `js/watch`. Update the hang draft and the docs -each one makes stale; rename CLI flags per the repo's CLI rule. +each one makes stale. Rename no CLI flag: that breaks callers, which m3 +cannot. -Public API: none left; the model renamed the CLI flag and archive keys. +Public API: none left. The model keeps `moq fetch --group` and the relay's +`/fetch?group=`, whose value now names the group starting there, and keys +archives by start. Wire: hang drops empty duration frames and discontinuity marker groups, which readers already tolerate.