quest: close the open-GOP fixture quest

quest/m0/interop-green/README.md

@@ -1,4 +1,4 @@
-# Interop and Video pass on main
+# [XS] Interop and Video pass on main
 
 ## Goal
 
@@ -8,9 +8,7 @@ means a new break. Interop has failed every scheduled run since
 
 ## Waiting
 
-- moq-dev/moq: a scheduled Interop run on `main` passes, once this quest's
-  fixture fixes, wire-compat remeasure, and 90-minute job budget have
-  landed. Check with
+- moq-dev/moq: a scheduled Interop run on `main` passes. Check with
   `gh run list --repo moq-dev/moq --workflow interop.yml --event schedule`.
   Triage any red run, then delete this quest once one passes.
 
@@ -29,8 +27,7 @@ port-reservation lines are negative self-tests in
 `interop/relay-log.test.sh` and `lib/harness.test.sh` that pass.
 Already owned: the intermittent media-matrix timestamp-gap cells
 (`cpp -> js-native-node`, `go -> c`, browser `rust -> js` timeouts) belong to
-[test flakes](/quest/m0/test-flakes-2/README.md), with
-[moq-dev/moq#6990](https://github.com/moq-dev/moq/pull/6990) open. So does
+[test flakes](/quest/m0/test-flakes-2/README.md). So does
 the fallback audio stall, which hit on
 `moq-lite-07-wip` in
 [41495461904](https://github.com/moq-dev/moq/actions/runs/41495461904) and
@@ -64,8 +61,11 @@ showed more causes, fixed in this quest's own PR:
 The P2P data-channel test timed out once, in 41668668824, and passes
 locally; triage it if it recurs.
 
-Public API: none. Wire: none.
-
-## Required
+Scheduled run
+[41863118968](https://github.com/moq-dev/moq/actions/runs/41863118968)
+(2026-11-04, after every fix above landed) passed the open-GOP recovery
+case, P2P, and wire-compat. Its only failure was the fallback audio stall
+above, on `moq-lite-07-wip` in Chromium, which the IETF22 fallback quest
+owns.
 
-- [Confirm scheduled open-GOP recovery passes](/quest/m0/interop-green/open-gop-fixture.md) - a scheduled Interop run passes the open-GOP case with the typed fixture and direct effect/page error reporting
+Public API: none. Wire: none.

quest/m0/test-flakes-2/ietf22-fallback.md

@@ -3,7 +3,7 @@
 ## Goal
 
 When the newest of two live publishers withdraws, a browser `@moq/watch`
-viewer on moq-transport-22, or on moq-lite in Firefox, plays the still-live
+viewer on moq-transport-22 or moq-lite plays the still-live
 older run within the media lane's derived 1039 ms bound. It keeps its session, and its audio resumes
 with its video. Both failures are fixed at their cause once one recurs with
 enough evidence to reproduce it deterministically.
@@ -30,7 +30,11 @@ after the fallback), on `old-moq-lite-07-wip`:
 and
 [2026-11-03](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988510133).
 [moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716) found it
-separate from the Firefox tone problem. Read those jobs' artifacts first. If
+separate from the Firefox tone problem. Scheduled Interop runs hit the same
+stall in Chromium, also on `old-moq-lite-07-wip`:
+[41495461904](https://github.com/moq-dev/moq/actions/runs/41495461904),
+[41668668824](https://github.com/moq-dev/moq/actions/runs/41668668824), and
+[41863118968](https://github.com/moq-dev/moq/actions/runs/41863118968). Read those jobs' artifacts first. If
 they isolate the cause, the Waiting item clears. If they don't, rerun the
 Waiting section's command with `--media-engines firefox` and the same
 `RUST_LOG` filter.