From ed40754bc16235712cc53aac2d8947d62b62c985 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sun, 8 Nov 2026 08:39:22 -0800 Subject: [PATCH] quest: intra-refresh recovery boundary moves back to m3 The maintainer dropped intra refresh from this cut. The boundary stays a catalog duration, never a LOC property, and the safe-bound question is re-asked in m3. Co-Authored-By: Claude Opus 5.5 --- quest/m2/README.md | 1 - quest/m3/intra-refresh/README.md | 2 +- quest/m3/intra-refresh/consumer-warmup.md | 2 +- quest/m3/intra-refresh/h264-import.md | 2 +- .../intra-refresh/recovery-boundary.md} | 16 ++++++++++++---- 5 files changed, 15 insertions(+), 8 deletions(-) rename quest/{m2/intra-refresh-boundary.md => m3/intra-refresh/recovery-boundary.md} (73%) diff --git a/quest/m2/README.md b/quest/m2/README.md index 15b2721d3ad..d52f568f65d 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -208,7 +208,6 @@ quests that require them. - [Bus writes land at a bus position](/quest/m2/bus-positioned-write.md) - callers sync audio to video without copying the bus's private latency, before the cut first publishes `bus` - [A mix-minus removes several sources](/quest/m2/bus-minus-several.md) - a guest's return feed drops every copy of their own sound - [Drop moq-auth's iroh transport](/quest/m2/auth-drop-iroh.md) - this breaking moq-auth release drops `Transport::Iroh` and the JS `"iroh"` value -- [Plan: recovery boundaries](/quest/m2/intra-refresh-boundary.md) - the catalog's new `warmup` contract is settled before the cut publishes it - [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 (held in m1 by an open claim) - [Finishing a producer returns a Finished handle](/quest/m2/finished-handle.md) - `finish(self)` consumes moq-net's and the media crates' producers, so appending after finish doesn't compile - [Cut readiness](/quest/m2/cut-gate/README.md) - the checks the cut needs that break nothing: main no slower than release, vendored fixes ported, and moq-c at parity diff --git a/quest/m3/intra-refresh/README.md b/quest/m3/intra-refresh/README.md index df1ca9fe9d5..c84d21e13ac 100644 --- a/quest/m3/intra-refresh/README.md +++ b/quest/m3/intra-refresh/README.md @@ -50,7 +50,7 @@ make these presentation guarantees true even when sweep lengths change. ## Required - [Dual decoder](/quest/m3/intra-refresh/dual-decoder.md) - js/watch's two decoders open on an H.264 recovery point in Firefox and Safari, as they now do in Chromium -- [Plan: recovery boundaries](/quest/m2/intra-refresh-boundary.md) - settle publication ordering for a later, longer sweep +- [Plan: recovery boundaries](/quest/m3/intra-refresh/recovery-boundary.md) - settle how a catalog `warmup` duration stays safe for a later, longer sweep - [Consumer warmup](/quest/m3/intra-refresh/consumer-warmup.md) - the transcoder decodes the groups covering `warmup` as history before each group, except at a true IDR - [H.264 import](/quest/m3/intra-refresh/h264-import.md) - the splitter keeps `recovery_frame_cnt` and import publishes `warmup` from it - [H.265 import](/quest/m3/intra-refresh/h265-import.md) - the splitter reads the recovery-point SEI so an HEVC intra-refresh stream forms groups and publishes `warmup` diff --git a/quest/m3/intra-refresh/consumer-warmup.md b/quest/m3/intra-refresh/consumer-warmup.md index 01b2ea619de..6acab564d5f 100644 --- a/quest/m3/intra-refresh/consumer-warmup.md +++ b/quest/m3/intra-refresh/consumer-warmup.md @@ -54,4 +54,4 @@ The fix is history rather than a withhold rule: ## Required -- [Plan: recovery boundaries](/quest/m2/intra-refresh-boundary.md) - K derives from `warmup`, which must be a safe upper bound +- [Plan: recovery boundaries](/quest/m3/intra-refresh/recovery-boundary.md) - K derives from `warmup`, which must be a safe upper bound diff --git a/quest/m3/intra-refresh/h264-import.md b/quest/m3/intra-refresh/h264-import.md index 43c8e19568b..2f6707aaff1 100644 --- a/quest/m3/intra-refresh/h264-import.md +++ b/quest/m3/intra-refresh/h264-import.md @@ -48,4 +48,4 @@ follows the hang draft, which rounds up ## Required -- [Plan: recovery boundaries](/quest/m2/intra-refresh-boundary.md) - resolve the later-mutated warmup contract before implementing it +- [Plan: recovery boundaries](/quest/m3/intra-refresh/recovery-boundary.md) - resolve the later-mutated warmup contract before implementing it diff --git a/quest/m2/intra-refresh-boundary.md b/quest/m3/intra-refresh/recovery-boundary.md similarity index 73% rename from quest/m2/intra-refresh-boundary.md rename to quest/m3/intra-refresh/recovery-boundary.md index 4985fbaf44b..5c651e13746 100644 --- a/quest/m2/intra-refresh-boundary.md +++ b/quest/m3/intra-refresh/recovery-boundary.md @@ -8,7 +8,15 @@ earlier ones. Rewrite the import and consumer quests around that contract. ## Plan -Moved from the m3 intra-refresh epic to m2: Decided 2026-11-07 (maintainer, /quest-plan from the API sweep of open PRs and remaining quests). The catalog's `warmup` field is new in this release, so its contract (a safe upper bound published before the content it covers) is settled before the cut publishes it. The implementation quests stay in m3. +Decided 2026-11-08 (maintainer, /quest-plan): moved back from m2. Intra +refresh is not part of this cut, so `warmup` ships with its current +duration contract and this plan settles only what the m3 importer needs. +The boundary stays a catalog field, never a LOC frame property or other +per-frame container field, and it is a duration, not a frame count. A +per-group exact boundary carried in the media was offered and declined. +Re-interview the maintainer before choosing how a catalog duration stays +safe when a later sweep is longer, since a catalog update and the groups +it covers travel on separate tracks with no ordering between them. The 2026-10-11 TS audit found the proposed catalog duration is not yet a sufficient guarantee. `h264-import` raises the global value after observing @@ -26,9 +34,9 @@ merged dual decoder in `decode::Consumer` ([#5842](https://github.com/moq-dev/moq/pull/5842)), and the draft now says so. Publication ordering for a later, longer sweep remains to settle. -Ask the maintainer to choose between an exact per-group boundary and a safe -bound known and published before the affected content, including the latency -and catalog/container consequences. Test timestamp precision, reordered +Ask the maintainer how the catalog duration stays safe for a longer sweep, +such as a bound published before the affected content or a fixed bound from +config, including the latency each costs. Test timestamp precision, reordered pictures, frame_num wrap, variable sweep lengths, a missed recovery picture, and a join/skip before a longer sweep is known. Decode-only pictures still build reference state; withholding presentation is not dropping their input.