From bdd9d91a772a699956c29bd933613cc21ec6b861 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 22 Oct 2026 17:59:03 -0700 Subject: [PATCH 1/3] chore(quest): claim quest/m0/release-fixed-delay.md Quest-Claim: d751ac8ecd4294a9 From 8b390f16193e8a5fd98b3d5acacc859b944192ab Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 22 Oct 2026 18:04:00 -0700 Subject: [PATCH 2/3] chore(quest): record fixed-delay deployment verification blocker Co-Authored-By: GPT-6 --- quest/m0/release-fixed-delay.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/quest/m0/release-fixed-delay.md b/quest/m0/release-fixed-delay.md index ea16a67b508..eba20f20d10 100644 --- a/quest/m0/release-fixed-delay.md +++ b/quest/m0/release-fixed-delay.md @@ -19,3 +19,34 @@ The backport preserves the behavior from breaking watch API rework: a numeric configured delay is used directly; "auto" and "instant" remain unchanged. The release-side tests and live-browser validation are recorded in the merged PR. Public API and wire are unchanged. + +### Verification + +Checked on 2026-10-23 UTC. The deployment condition is still unmet: + +- [Release JS at the backport merge](https://github.com/moq-dev/moq/actions/runs/39810032442) + succeeded, but its publish log says `@moq/watch@0.6.3 already published, + skipping` at 2026-10-22T16:15:45Z. A green run does not establish that the + changed package was published. +- The site's [lockfile at 8a7eec8](https://github.com/moq-dev/moq.dev/blob/8a7eec8e4be43127d33b4e88ad64a49cbb8fb4b6/bun.lock#L318) + resolves `@moq/watch` to 0.6.2. This source pin does not identify the deployed + build by itself. +- In a fresh Chrome tab, the [live demo](https://moq.dev/watch/?project=demo&name=bbb.hang) + played video. Settings > Latency showed an active 100 ms preset with + **Jitter buffer 100 ms / Total buffer 475 ms**, then an active 250 ms preset + with **250 ms / 625 ms**. Returning to 100 ms repeated **100 ms / 475 ms**. + These are the player's displayed buffer diagnostics, not a glass-to-glass + measurement or proof that the extra 375 ms comes from particular catalog + fields. +- The browser observed `/_astro/watch.DDINuY1C.js` and + `/_astro/element.gftmzwNG.js`. No deployed revision was exposed, and the + browser's asset export does not support scripts, so the deployed fixed-delay + branch was not verified from these asset names. + +Keep this quest until a package containing the backport is published and the +site deploy uses it. Then establish deployed build provenance and repeat the +numeric selections against nonzero, changing catalog delay/jitter, using the +resolved total-buffer diagnostic or controlled playback. The numeric target +must remain 100/250 ms as those estimates change. Release versioning and site +deployment remain outside this verification checkpoint; do not duplicate the +backport. From f9155445fa69054aca563c22161980b82ea1122c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Fri, 23 Oct 2026 02:16:44 -0700 Subject: [PATCH 3/3] docs: verify published fixed-delay watch package Co-Authored-By: GPT-6 --- quest/m0/release-fixed-delay.md | 38 +++++++++++++++++++++------------ 1 file changed, 24 insertions(+), 14 deletions(-) diff --git a/quest/m0/release-fixed-delay.md b/quest/m0/release-fixed-delay.md index eba20f20d10..c3c535a3509 100644 --- a/quest/m0/release-fixed-delay.md +++ b/quest/m0/release-fixed-delay.md @@ -11,8 +11,9 @@ contains the fix and numeric selections no longer include those estimates. The implementation merged into release in [moq-dev/moq#6217](https://github.com/moq-dev/moq/pull/6217). Verify its release -deploy reaches moq.dev, then retire this quest; no duplicate backport is -needed. +deploy reaches moq.dev, then retire this quest. Published `@moq/watch@0.6.5` +contains the fix; the remaining condition is the site's dependency, +deployment provenance, and live verification. No duplicate backport is needed. The backport preserves the behavior from [moq-dev/moq#4162](https://github.com/moq-dev/moq/pull/4162) without its @@ -22,16 +23,25 @@ validation are recorded in the merged PR. Public API and wire are unchanged. ### Verification -Checked on 2026-10-23 UTC. The deployment condition is still unmet: - -- [Release JS at the backport merge](https://github.com/moq-dev/moq/actions/runs/39810032442) - succeeded, but its publish log says `@moq/watch@0.6.3 already published, - skipping` at 2026-10-22T16:15:45Z. A green run does not establish that the - changed package was published. -- The site's [lockfile at 8a7eec8](https://github.com/moq-dev/moq.dev/blob/8a7eec8e4be43127d33b4e88ad64a49cbb8fb4b6/bun.lock#L318) - resolves `@moq/watch` to 0.6.2. This source pin does not identify the deployed - build by itself. -- In a fresh Chrome tab, the [live demo](https://moq.dev/watch/?project=demo&name=bbb.hang) +Checked on 2026-10-23 UTC. Package publication is proven; the site's deployment +condition remains unverified: + +- The [published 0.6.5 package metadata](https://registry.npmjs.org/@moq/watch/0.6.5) + identifies commit + [4f401ab](https://github.com/moq-dev/moq/commit/4f401ab94e00ae97134b8ad608e08d371c662ab4). + Its [published archive](https://registry.npmjs.org/@moq/watch/-/watch-0.6.5.tgz) + contains `player-DVWG4_Zd.js`: its numeric branch sets the resolved delay + directly and returns before adding media delay and jitter. The accompanying + `player-DVWG4_Zd.js.map` embeds `../src/sync.ts`; its `#runDelay` contains the + exact numeric early return from the backport. This verifies changed package + bytes, independently of the earlier successful Release JS run that skipped + already-published 0.6.3. +- The site's current main remains + [8a7eec8](https://github.com/moq-dev/moq.dev/commit/8a7eec8e4be43127d33b4e88ad64a49cbb8fb4b6). + Its [lockfile](https://github.com/moq-dev/moq.dev/blob/8a7eec8e4be43127d33b4e88ad64a49cbb8fb4b6/bun.lock#L318) + still resolves `@moq/watch` to 0.6.2. This source pin does not identify the + deployed build by itself, and no deployed revision was established. +- In the earlier fresh Chrome tab, the [live demo](https://moq.dev/watch/?project=demo&name=bbb.hang) played video. Settings > Latency showed an active 100 ms preset with **Jitter buffer 100 ms / Total buffer 475 ms**, then an active 250 ms preset with **250 ms / 625 ms**. Returning to 100 ms repeated **100 ms / 475 ms**. @@ -43,8 +53,8 @@ Checked on 2026-10-23 UTC. The deployment condition is still unmet: browser's asset export does not support scripts, so the deployed fixed-delay branch was not verified from these asset names. -Keep this quest until a package containing the backport is published and the -site deploy uses it. Then establish deployed build provenance and repeat the +Keep this quest until the site deploy uses the corrected package. Establish +deployed build provenance and repeat the numeric selections against nonzero, changing catalog delay/jitter, using the resolved total-buffer diagnostic or controlled playback. The numeric target must remain 100/250 ms as those estimates change. Release versioning and site