Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion quest/m2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,6 @@ quests that require them.
- [JS time values are types, not numbers](/quest/m2/js-time-types.md) - every public JS duration and instant is a `Clock.Duration` or `Clock.Instant` object, so a unit mistake fails to compile
- [Small API fixes before the cut](/quest/m2/api-shape/README.md) - one path and one spelling per item, names by role, and no dead or wrong-role public surface across net, transport, media, native, apps, JS, and bindings
- [Public constructors spawn nothing, or say why](/quest/m2/spawn-constructors.md) - each public library entry point that spawns returns a driver its caller polls, or is listed as kept
- [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
Expand Down
2 changes: 1 addition & 1 deletion quest/m3/intra-refresh/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
2 changes: 1 addition & 1 deletion quest/m3/intra-refresh/consumer-warmup.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
2 changes: 1 addition & 1 deletion quest/m3/intra-refresh/h264-import.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.
Expand Down