diff --git a/quest/m1/interop-coverage/README.md b/quest/m1/interop-coverage/README.md
index edeadc2436a..3f1326fd5c3 100644
--- a/quest/m1/interop-coverage/README.md
+++ b/quest/m1/interop-coverage/README.md
@@ -45,7 +45,6 @@ coverage on `main` at `3ab6cbf81d`.
 ## Required
 
 - [Draft-18 TRACK_STATUS FIN](/quest/m1/interop-coverage/draft18-status-fin.md) - a draft-18 TRACK_STATUS followed at once by a FIN is answered, so moqx-forwarded status requests reach moq-dev publishers
-- [JS subgroup data through imquic](/quest/m1/interop-coverage/js-imquic-objects.md) - the runner's moq-dev-js client moves to an `@moq/net` patch that writes data stream headers in one write, so data-subgroup-basic passes against imquic
 - [JS subscribers FETCH](/quest/m1/interop-coverage/js-ietf-fetch.md) - `@moq/net` fetches past groups over moq-transport, and joins the CLI FETCH round
 
 ## Related
diff --git a/quest/m1/interop-coverage/js-imquic-objects.md b/quest/m1/interop-coverage/js-imquic-objects.md
deleted file mode 100644
index 98ad864939d..00000000000
--- a/quest/m1/interop-coverage/js-imquic-objects.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# [XS] The runner's JS client writes data stream headers in one write
-
-## Goal
-
-Condition: the next `@moq/net` patch release, 0.4.7 or later, ships from
-`release` carrying [moq-dev/moq#6769](https://github.com/moq-dev/moq/pull/6769),
-the JS-only `release` backport of
-[moq-dev/moq#6504](https://github.com/moq-dev/moq/pull/6504). Check that
-`npm view @moq/net version` is above 0.4.6 and that
-`git log origin/release -- js/net/package.json` shows a bump after the
-backport merged. Releases are cut separately; this quest bumps nothing.
-
-Then bump `@moq/net` in the moq-dev-js client of
-[englishm/moq-interop-runner](https://github.com/englishm/moq-interop-runner)
-to it, so `data-subgroup-basic` passes against imquic (draft-22,
-WebTransport), and delete this quest once that PR merges. If imquic fixes
-[meetecho/imquic#43](https://github.com/meetecho/imquic/issues/43) first and
-the runner rebuilds its image, the cell turns green without the bump; delete
-the quest then.
-
-## Plan
-
-imquic drops a SUBGROUP_HEADER or FETCH_HEADER that arrives across more
-than one stream read, so the relay discards every object and logs
-`No track found for that subscription` with alias 0 at the stream's FIN.
-`@moq/net` 0.4.6 and earlier write the header one field per write, which
-the polyfill sends as separate frames. `main` writes it in one write since
-#6504, and the backport does the same on `release`. Against the runner's
-imquic relay image, the runner's client fails every run on 0.4.4 and passes
-3/3 on the backport branch.
-
-The runner's client must stay on the 0.4 line for this: `main`'s announced
-request watches the tuple's exact path, which moq-transport relays answer
-only with namespaces beneath it, so it never discovers the shorter routing
-prefix the publisher claimed. That is recorded on
-[Runner client bump](/quest/m2/release/runner-client-bump.md), which moves
-the client to `main`'s cut.
-
-The interop audit's standing approval covers PRs touching the `moq-dev-*`
-builds.
diff --git a/quest/m2/audit-interop.md b/quest/m2/audit-interop.md
index b2cc6869895..7e1b5b9fb98 100644
--- a/quest/m2/audit-interop.md
+++ b/quest/m2/audit-interop.md
@@ -118,8 +118,12 @@ Theirs, reported or waiting on others:
   fixed upstream; imquic's cells against `cdn.moq.dev` wait for the runner
   to rebuild its image.
   [meetecho/imquic#43](https://github.com/meetecho/imquic/issues/43)
-  (drops a data stream whose header spans reads) is owned by
-  [JS subgroup data through imquic](/quest/m1/interop-coverage/js-imquic-objects.md).
+  (drops a data stream whose header spans reads) is closed, and the
+  runner's moq-dev-js client writes the header in one write since
+  `@moq/net` 0.4.7
+  ([englishm/moq-interop-runner#179](https://github.com/englishm/moq-interop-runner/pull/179)):
+  `data-subgroup-basic` against imquic passes in all three cells of the
+  2026-10-31 nightly.
   [Eyevinn/moqlivemock#157](https://github.com/Eyevinn/moqlivemock/issues/157)
   is fixed and green.
 - Drafted in this run, posted only if the maintainer approved: MOQtail draft-18 never forwards
@@ -152,7 +156,9 @@ and moqtopus and xquic-draft-18 over WebTransport (raw QUIC only).
 
 From the 2026-10-25 run: the runner's moq-dev-js `announce-subscribe` case times
 out against imquic on both 0.4.4 and the [moq-dev/moq#6769](https://github.com/moq-dev/moq/pull/6769)
-backport, so it predates that fix. Classify it.
+backport, so it predates that fix. It still times out on 0.4.6 and 0.4.7
+(2026-10-28, 3 runs each), and fails in all three moq-dev-js → imquic
+cells of the 2026-10-31 nightly. Classify it.
 
 ## Related