Repository navigation
quest: record the maintainer's 2026-11-15 answers to waiting items - #8870
Conversation
Settle sixteen Waiting items from /quest-complete, delete resume-redesign and recovery-boundary, split the Windows GPU tests into their own m4 quest, and defer ffi-exporter's decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 30 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — quest-only text edits recording the maintainer's 2026-11-15 answers. I spot-checked for dangling references only, not the full diff.
- Deleted quests —
resume-redesign.mdandintra-refresh/recovery-boundary.mdare gone, and nothing inquest/ordoc/still references them. - New quest —
quest/m4/windows-gpu-tests.mdexists, split out ofvideo-hardware.md. - Rewrites — the other edits record decisions in their quests' Plans (
gpu-ci,cli-packaging,announce-interest-memory,quic-ack-hookand others).
claude-sonnet-5-5 | 𝕏
Split the websocket::accept reshape into its own m2 quest, end lite-05/06 tails with an error when no max delay is set, and move quic-ack-hook to m4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Incremental review of the follow-up commit since the prior pullfrog review.
- Split the WebSocket driver handoff into the new
quest/m2/websocket-accept-driver.md, listed inrelay.mdRequired. - Moved
quic-ack-hooktoquest/m4/and updated its links inquic-deadline.md. No references to the old m3 path remain. - Tightened
lite-tail-drop-count.mdso a lite-05/06 tail with no max delay errors too. - Recorded the nuts-rice ask in
vr-demo-try.md.
claude-sonnet-5-5 | 𝕏
#8870 deleted quest/m4/intra-refresh/recovery-boundary.md on the maintainer's answers; the deletion stands over this branch's reword.

Problem
On 2026-11-15 the maintainer answered the quest
## Waitingitems walked by/quest-complete. Each answer has to be recorded in its quest's Plan and the item removed, and quests whose only purpose was a wait have to go.Approach
quest/m3/gpu-ci.md: records the sandboxed-container runner and drops the VFIO passthrough text.quest/m3/cli-packaging.md: records wait-then-fork;quest/m3/cpal-alsa-runtime.md's fork fallback now cites it instead of "the maintainer decides".quest/m3/capture-linux.md,quest/m3/capture-windows.md: record window capture only.Source::Appalready returnsUnsupported("application capture")off macOS (rs/moq-video/src/capture/mod.rs), so both Goals drop app capture as work.quest/m3/lite-tail-drop-count.md: records the max-delay wait, and an error on lite-05/06 and lite-07 when no max delay is set.quest/m3/webrtc-dial-policy.md: records the moq-net value type reached through the two#[non_exhaustive]configs.quest/m3/quic-ack-hook.md, moved withquest mvtoquest/m4/quic-ack-hook.md(links inquic-deadline.mdfollow): Goal and Plan rewritten to the trap tests on the crate-private methods; the publicpoll_acked/acked/offset()API is dropped. Kept at[S](the item suggested XS), since it is about nine trap cases through two drivers.quest/m4/resume-redesign.md: deleted withquest rm;quest/m4/resume-trace-validation.md's check-the-redesign bullet now says the per-reader path stays.quest/m4/announce-interest-memory.md: rewritten from the shared-snapshot redesign to asession::Limitscap on lite-05/06 and moq-transport interest streams ([M]to[S];Limitsis#[non_exhaustive], so the field is additive).quest/m4/binding-export-coverage.md: builds the list only from the exporter and gainsquest/m3/ffi-exporter.mdin## Required.quest/m4/browser-reset-reports.md: records approval to file at crbug.com and bugzilla.mozilla.org after each tracker's LLM policy check.quest/m4/upstream-reports.md: drops the GStreamerfaad, retina, and mr-boxington reports. The approved Chromium and Firefox reports and the already-filed Biome follow-through remain, so the quest stays (retitled "Report approved upstream bugs") and its approved filings get the same LLM-policy check.quest/m4/quic-interop-listing.md: records approval to register once every supported case passes against two peers.quest/m4/intra-refresh/recovery-boundary.md: deleted withquest rm; its decision lives in the epic README's shared decisions, and its leftover test and codec-review guidance moved intoh264-import.mdandh265-import.md.consumer-warmup.mdnotes why a stalewarmupstill leaves the transcoder's one group of history clean.quest/m5/video-hardware.md: the Windows GPU probes and dx12 export tests split into the newquest/m4/windows-gpu-tests.md([M],## Hostswindows), linked Related both ways.mediafoundation_camera_texturestays in the parent, since thewindowshost has no camera.quest/m5/video-hardware-access.mdpoints at the split.quest/m9/stream-transports/relay.md: records reshapingmoq_tokio::websocket::accept, split into the newquest/m2/websocket-accept-driver.md([S], top-level m2 since no m2 epic fits), which relay.md now lists in Required. The new quest notes that SETUP is read with the driver running, so the driver comes back once QMux is established rather than at the end, and that its PR is!with a migration note in Impact.quest/m1/vr-demo-try.md: the Maintainer item becomes anuts-rice:item naming the ask in moq-dev/moq#8781.quest/m3/ffi-exporter.md: keeps its Waiting item and gains aDeferred 2026-11-15line.Decisions
All by the maintainer on 2026-11-15 in
/quest-complete:Source::Appstays macOS-only (rejected: (B) compose app capture).#[non_exhaustive]configs (rejected: (b) moq-tokio; (c) its own crate).quest rm: it only waited on that decision.session::Limitscap for lite-05/06 and moq-transport now, deleted once lite-07 is the oldest version served (rejected: the shared snapshot redesign; deleting later with no cap).faad, retina idlePending, and mr-boxington eviction (rejected: (a) approve).warmup: ✅ a hint nothing enforces (rejected: refuse the stream; a published-ahead bound; a fixed config bound). Since moq-dev/moq#8857 a longer sweep only shows stripes a little longer. That left recovery-boundary with no work of its own, so it was removed withquest rmand its Required links dropped fromh264-import.mdandconsumer-warmup.md.windows-host items into a new m4 quest (rejected: the lab; keep together).moq_tokio::websocket::accept(rejected: an additive sibling), ✅ as its own m2 quest that relay.md requires (rejected: land it with the rust2 migration).Impact
None: quest text only. No public API or wire change.
Validation
nix develop --command bash sh/quest.sh check(pinned quest3122d76):quest: 488 documents okon the second commit. Checked thatSource::Appalready refuses off macOS, that moq-webrtc and moq-rtmp both depend on moq-net, thatsession::Limitsis#[non_exhaustive], that every test the new Windows quest names exists, and that the comment asking nuts-rice exists.Models
Size: M
Implementer: Claude Code, claude-opus-5-5, medium effort
(Written by Claude Opus 5.5)
Review
Rewritten by
quest reviewafter each round.Head: b447433
Base: origin/main at 813f7a0
Risk: medium,
the base has no RISK.md to name what is always high or customer-facing, so every change is mediumClassified: medium by default
Reviewer: Codex, gpt-6.1-sol, high effort
Session:
01a1e105-0994-7802-a6b9-677f80ee9120, round 2Score: 10/10,
The incremental quest changes consistently separate the WebSocket API work, clarify tail handling, and update references for the moved ACK validation plan; no actionable defects were found.Rounds: 2; first round 0; findings 0: fixed 0, refuted 0, open 0
Findings: none