From 55b0bf1700da57d244104a7953ce956e82505dbd Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 13:25:09 -0800 Subject: [PATCH 1/7] quest: unblock the dart tag push, OSS-Fuzz application, and the nixpkgs review Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 10 ++-------- .../m2/cluster-routing/routes/playwright-pin.md | 5 ++++- quest/m4/oss-fuzz.md | 16 +++++++--------- 3 files changed, 13 insertions(+), 18 deletions(-) diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index 8a730d5f1db..b9da366a13d 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -42,17 +42,11 @@ Decided 2026-11-09 (maintainer, /quest-unblock): ✅ an agent pushes PR, [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378), merges (rejected: tag before #8378 merges; the maintainer pushes it). Then it checks that `release-dart.yml` succeeds and pub.dev lists 0.1.1, and deletes this -quest. +quest. [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378) merged +2026-11-11, so the tag push is ready. Public API: none. Wire: none. -## Waiting - -- moq-dev/moq: the combined patch cut's release-plz PR, - [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378), merges into - `release`. Check with `gh pr view 8378 --repo moq-dev/moq --json state`; - then push the tag as the Plan's 2026-11-09 decision says. - ## Related - [A Dart tag publishes unattended](/quest/m3/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses diff --git a/quest/m2/cluster-routing/routes/playwright-pin.md b/quest/m2/cluster-routing/routes/playwright-pin.md index fd315fb268d..3ee784f8a04 100644 --- a/quest/m2/cluster-routing/routes/playwright-pin.md +++ b/quest/m2/cluster-routing/routes/playwright-pin.md @@ -42,4 +42,7 @@ rebuild and pin browser binaries outside nixpkgs. [NixOS/nixpkgs#585789](https://github.com/NixOS/nixpkgs/pull/585789) (it also fixes `update.sh` for 1.65's SHA-pinned driver version and rebases the python driver patch). Advance it by answering that PR's review; then wait - for it to reach `nixpkgs-unstable`. + for it to reach `nixpkgs-unstable`. Decided 2026-11-11 (maintainer, + /quest-unblock): an agent drafts each review fix on the fork's branch with + an `Assisted-by:` trailer, as nixpkgs' CONTRIBUTING.md requires, and the + maintainer reviews the diff and reply before anything is pushed or posted. diff --git a/quest/m4/oss-fuzz.md b/quest/m4/oss-fuzz.md index b11c214f7e3..158c6454a67 100644 --- a/quest/m4/oss-fuzz.md +++ b/quest/m4/oss-fuzz.md @@ -7,15 +7,6 @@ clock, keeping its own corpus. A crash it finds reaches the maintainer privately, and its reproducer lands in the target's `regressions/` so `just check` replays it. -## Waiting - -- Maintainer: approve the application PR to - [google/oss-fuzz](https://github.com/google/oss-fuzz) and name the contact - address it lists. An agent cannot take this: it posts outside the - `kixelated` and `moq-dev` orgs, the address receives private security - reports, and accepting commits the project to OSS-Fuzz's 90-day disclosure - deadline. Done when the application PR is open. - ## Plan Decided 2026-11-10 (maintainer, /quest-plan of the follow-ups from @@ -26,6 +17,13 @@ Decided 2026-11-10 (maintainer, /quest-plan of the follow-ups from - ✅ m4, after the whole-session targets exist, since stateful targets gain the most from long runs. +Decided 2026-11-11 (maintainer, /quest-unblock): ✅ the project files list +`security@moq.dev`, the address in `SECURITY.md` (rejected: a personal +address), and ✅ the agent opens the google/oss-fuzz PR from the +maintainer's account once the maintainer has reviewed its draft files and PR +text (rejected: waiting to decide). The maintainer accepts OSS-Fuzz's 90-day +disclosure deadline. + Nightly gives each of its 22 codec targets five minutes and the two whole-session targets (`session_lite`, `session_ietf`) fifteen. That finds shallow bugs and replays the corpus; it rarely reaches deep states, and the From 4f6a015de21e2b5c4fd817cbc29c17f7663bd42b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:06:24 -0800 Subject: [PATCH 2/7] quest: add test-lints hang follow-up Co-Authored-By: Claude Opus 5.5 --- quest/m0/test-lints-hang.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 quest/m0/test-lints-hang.md diff --git a/quest/m0/test-lints-hang.md b/quest/m0/test-lints-hang.md new file mode 100644 index 00000000000..c67a4bc4d7a --- /dev/null +++ b/quest/m0/test-lints-hang.md @@ -0,0 +1,14 @@ +# [XS] `test-lints.test.py` hangs `just check` + +## Goal + +`python3 sh/rs/test-lints.test.py` finishes, so `just gh test`, which every +`just check` runs, ends instead of hanging until it is killed. + +## Plan + +Seen 2026-11-11: on `origin/main` (f190d90b34) the script prints one `.` and +then makes no progress for 5 minutes; inside `just check` it ran 80 minutes +before being killed. Reproduce it with `timeout 300 python3 +sh/rs/test-lints.test.py`, find what the second test waits on, and fix the +root cause. From 1df96effeb675c4ba83fabe1768abeefeeb55c61 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:06:30 -0800 Subject: [PATCH 3/7] quest: plain test-lints hang title Co-Authored-By: Claude Opus 5.5 --- quest/m0/test-lints-hang.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quest/m0/test-lints-hang.md b/quest/m0/test-lints-hang.md index c67a4bc4d7a..b0551c7ba0f 100644 --- a/quest/m0/test-lints-hang.md +++ b/quest/m0/test-lints-hang.md @@ -1,4 +1,4 @@ -# [XS] `test-lints.test.py` hangs `just check` +# [XS] test-lints.test.py hangs just check ## Goal From 397fb9956c889a1bb2b0e99ade17b4c25f1a963c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:14:22 -0800 Subject: [PATCH 4/7] quest: record why test-lints.test.py stalls Co-Authored-By: Claude Opus 5.5 --- quest/m0/test-lints-hang.md | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/quest/m0/test-lints-hang.md b/quest/m0/test-lints-hang.md index b0551c7ba0f..8dc43b4784a 100644 --- a/quest/m0/test-lints-hang.md +++ b/quest/m0/test-lints-hang.md @@ -1,14 +1,23 @@ -# [XS] test-lints.test.py hangs just check +# [XS] test-lints.test.py stalls just check on a busy host ## Goal -`python3 sh/rs/test-lints.test.py` finishes, so `just gh test`, which every -`just check` runs, ends instead of hanging until it is killed. +`python3 sh/rs/test-lints.test.py` finishes in seconds however loaded the +host is, so `just gh test`, which every `just check` runs, never stalls on it. ## Plan Seen 2026-11-11: on `origin/main` (f190d90b34) the script prints one `.` and then makes no progress for 5 minutes; inside `just check` it ran 80 minutes -before being killed. Reproduce it with `timeout 300 python3 -sh/rs/test-lints.test.py`, find what the second test waits on, and fix the -root cause. +before being killed. The same day another `just check` passed it on a quieter +host. + +Decided 2026-11-11 (maintainer, /quest-unblock pick of +[moq-dev/moq#8517](https://github.com/moq-dev/moq/pull/8517)): ✅ keep this +quest, with this diagnosis (rejected: dropping it). The `.` is +`test_clippy_warning_fails_test_build`, which sets `LOCAL_SUPERVISED=1`. +`test_fail_fast_environment_reaches_nextest` does not, so each of its 18 +`just rs test` calls goes through `sh/local.sh` to `quest gate` and waits for +host room; on a loaded host that never comes in useful time. Set +`LOCAL_SUPERVISED=1` in its env as the clippy test does, and confirm the +script finishes while other gated work holds the host. From 26b777acdc2dfa7c30785ba871c0f83dd0c140b2 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:15:35 -0800 Subject: [PATCH 5/7] quest: record the failed dart publish and nixpkgs reply disclosure Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 14 +++++++++++++- quest/m2/cluster-routing/routes/playwright-pin.md | 3 ++- quest/m3/release/dart-publish.md | 6 ++++-- 3 files changed, 19 insertions(+), 4 deletions(-) diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index b9da366a13d..767f48fa3ea 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -43,10 +43,22 @@ PR, [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378), merges (rejected: tag before #8378 merges; the maintainer pushes it). Then it checks that `release-dart.yml` succeeds and pub.dev lists 0.1.1, and deletes this quest. [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378) merged -2026-11-11, so the tag push is ready. +2026-11-11, so the agent pushed `moq-dart-v0.1.1`; `release-dart.yml` +published nothing because pub.dev's automated publishing is not enabled for +`moq-dev/moq` +([run 43107848443](https://github.com/moq-dev/moq/actions/runs/43107848443)). +Once the maintainer enables it, an agent re-runs that workflow; the tag +already points at the right commit and pub.dev rejected the upload at +authentication, so no version is burned. Public API: none. Wire: none. +## Waiting + +- Maintainer: enable automated publishing for `moq` on pub.dev (repository + `moq-dev/moq`, tag pattern `moq-dart-v{{version}}`); only a package admin + signed in to pub.dev can. Check: re-running run 43107848443 publishes 0.1.1. + ## Related - [A Dart tag publishes unattended](/quest/m3/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses diff --git a/quest/m2/cluster-routing/routes/playwright-pin.md b/quest/m2/cluster-routing/routes/playwright-pin.md index 3ee784f8a04..64d12908f2e 100644 --- a/quest/m2/cluster-routing/routes/playwright-pin.md +++ b/quest/m2/cluster-routing/routes/playwright-pin.md @@ -44,5 +44,6 @@ rebuild and pin browser binaries outside nixpkgs. python driver patch). Advance it by answering that PR's review; then wait for it to reach `nixpkgs-unstable`. Decided 2026-11-11 (maintainer, /quest-unblock): an agent drafts each review fix on the fork's branch with - an `Assisted-by:` trailer, as nixpkgs' CONTRIBUTING.md requires, and the + an `Assisted-by:` trailer, as nixpkgs' CONTRIBUTING.md requires, plus a separate AI-disclosure line in + the reply itself, which that policy requires apart from commits; the maintainer reviews the diff and reply before anything is pushed or posted. diff --git a/quest/m3/release/dart-publish.md b/quest/m3/release/dart-publish.md index ee3654ee79a..0b2e7df9742 100644 --- a/quest/m3/release/dart-publish.md +++ b/quest/m3/release/dart-publish.md @@ -16,8 +16,10 @@ trusted publishing is still unproven. Trusted-publishing configuration and checks of already-published artifacts can proceed independently; cutting the tag cannot. -- Confirm trusted publishing is configured for `moq` (repository - `moq-dev/moq`, tag pattern `moq-dart-v{{version}}`). +- Configure trusted publishing for `moq` (repository `moq-dev/moq`, tag + pattern `moq-dart-v{{version}}`): the `moq-dart-v0.1.1` tag showed it is not + enabled for `moq-dev/moq`, likely still bound to the pre-org repository, as + [ffi-shutdown-backport](/quest/m0/ffi-shutdown-backport.md) waits on. - Raise `dart/moq/pubspec.yaml`'s `moq_ffi` floor to the release the wrapper now needs (the media namespace and codec types), since `^0.4.3` resolves bindings without them. - Cut the next `moq-dart-v*` release with the binding breaks and confirm the workflow publishes it. - Verify the published `moq_ffi` resolves its native asset from a clean From eedcc3a24d382df505fa47349500a064322895f2 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:26:40 -0800 Subject: [PATCH 6/7] quest: dart 0.1.1 published; finish the ffi backport and fix the gated-run count Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 64 ------------------------------- quest/m0/test-lints-hang.md | 6 +-- quest/m3/release/dart-publish.md | 11 ++++-- 3 files changed, 10 insertions(+), 71 deletions(-) delete mode 100644 quest/m0/ffi-shutdown-backport.md diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md deleted file mode 100644 index 767f48fa3ea..00000000000 --- a/quest/m0/ffi-shutdown-backport.md +++ /dev/null @@ -1,64 +0,0 @@ -# [XS] Publish the release line's drain() wrappers - -## Goal - -The `release` line's hand-written Dart wrapper that gained `drain()` in -[moq-dev/moq#6642](https://github.com/moq-dev/moq/pull/6642), Dart -[`moq`](https://pub.dev/packages/moq) 0.1.1, is on pub.dev. - -Check: pub.dev lists the version. It is already set on `release` -(`dart/moq/pubspec.yaml`), so this needs a tag push, not code. - -## Plan - -Already published (checked 2026-10-31): moq-ffi 0.4.19 carries `drain()` and -qmux 0.5.3 on PyPI, Maven Central, and pub.dev; moq-ffi 0.4.20 followed. -Swift `Moq` 0.5.2 is tagged, and Kotlin `dev.moq:moq` 0.5.3 is on Maven Central -from `gh workflow run release-kt-lib.yml --ref release` -([run](https://github.com/moq-dev/moq/actions/runs/40904381781), after -[moq-dev/moq#7026](https://github.com/moq-dev/moq/pull/7026)'s fix). - -Python [`moq-rs`](https://pypi.org/project/moq-rs/) 0.5.2 reached PyPI on -2026-10-31. - -Decided 2026-10-30 (maintainer): Dart `moq` 0.1.1 ships in the next combined -patch cut on `release`, which the maintainer cuts. - -Dart: pub.dev publishes `moq` only from a `moq-dart-v*` tag, and only -`moq-dart-v0.1.0` exists. Pushing `moq-dart-v0.1.1` at `release`'s head -publishes 0.1.1 and exercises the unproven path in -[A Dart tag publishes unattended](/quest/m3/release/dart-publish.md). Decided -2026-10-30 (maintainer): push it during the combined cut, not before. - -Decided 2026-11-04 (maintainer, /quest-unblock): ✅ cut the combined patch -release on `release` soon, once [moq-dev/moq#7596](https://github.com/moq-dev/moq/pull/7596)'s -remaining ports and [moq-dev/moq#7680](https://github.com/moq-dev/moq/pull/7680) -are ready, and merge `main` into `release` for the next minor line -separately, later. Not chosen: one combined cut that merges `main` first, or -neither this week. - -Decided 2026-11-09 (maintainer, /quest-unblock): ✅ an agent pushes -`moq-dart-v0.1.1` at `release`'s head once the combined cut's release-plz -PR, [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378), merges -(rejected: tag before #8378 merges; the maintainer pushes it). Then it checks -that `release-dart.yml` succeeds and pub.dev lists 0.1.1, and deletes this -quest. [moq-dev/moq#8378](https://github.com/moq-dev/moq/pull/8378) merged -2026-11-11, so the agent pushed `moq-dart-v0.1.1`; `release-dart.yml` -published nothing because pub.dev's automated publishing is not enabled for -`moq-dev/moq` -([run 43107848443](https://github.com/moq-dev/moq/actions/runs/43107848443)). -Once the maintainer enables it, an agent re-runs that workflow; the tag -already points at the right commit and pub.dev rejected the upload at -authentication, so no version is burned. - -Public API: none. Wire: none. - -## Waiting - -- Maintainer: enable automated publishing for `moq` on pub.dev (repository - `moq-dev/moq`, tag pattern `moq-dart-v{{version}}`); only a package admin - signed in to pub.dev can. Check: re-running run 43107848443 publishes 0.1.1. - -## Related - -- [A Dart tag publishes unattended](/quest/m3/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses diff --git a/quest/m0/test-lints-hang.md b/quest/m0/test-lints-hang.md index 8dc43b4784a..94528bc34e8 100644 --- a/quest/m0/test-lints-hang.md +++ b/quest/m0/test-lints-hang.md @@ -16,8 +16,8 @@ Decided 2026-11-11 (maintainer, /quest-unblock pick of [moq-dev/moq#8517](https://github.com/moq-dev/moq/pull/8517)): ✅ keep this quest, with this diagnosis (rejected: dropping it). The `.` is `test_clippy_warning_fails_test_build`, which sets `LOCAL_SUPERVISED=1`. -`test_fail_fast_environment_reaches_nextest` does not, so each of its 18 -`just rs test` calls goes through `sh/local.sh` to `quest gate` and waits for -host room; on a loaded host that never comes in useful time. Set +`test_fail_fast_environment_reaches_nextest` does not, so each of its 20 +runs (10 through `just rs test`, 10 calling `sh/rs/nextest.sh` directly) goes +through `sh/local.sh` to `quest gate` and waits for host room; on a loaded host that never comes in useful time. Set `LOCAL_SUPERVISED=1` in its env as the clippy test does, and confirm the script finishes while other gated work holds the host. diff --git a/quest/m3/release/dart-publish.md b/quest/m3/release/dart-publish.md index 0b2e7df9742..4a57b6bde99 100644 --- a/quest/m3/release/dart-publish.md +++ b/quest/m3/release/dart-publish.md @@ -16,10 +16,13 @@ trusted publishing is still unproven. Trusted-publishing configuration and checks of already-published artifacts can proceed independently; cutting the tag cannot. -- Configure trusted publishing for `moq` (repository `moq-dev/moq`, tag - pattern `moq-dart-v{{version}}`): the `moq-dart-v0.1.1` tag showed it is not - enabled for `moq-dev/moq`, likely still bound to the pre-org repository, as - [ffi-shutdown-backport](/quest/m0/ffi-shutdown-backport.md) waits on. +- Trusted publishing for `moq` is fixed: its repository field read + `moq/moq-dev` (owner and name swapped), so pub.dev refused the + `moq-dart-v0.1.1` tag's token. On 2026-11-11 the maintainer set it to + `moq-dev/moq` (tag pattern `moq-dart-v{{version}}`, environment `pub.dev`, + push events), and a rerun of that tag's + [release-dart run](https://github.com/moq-dev/moq/actions/runs/43107848443) + published 0.1.1. The next tag shows whether it publishes with no rerun. - Raise `dart/moq/pubspec.yaml`'s `moq_ffi` floor to the release the wrapper now needs (the media namespace and codec types), since `^0.4.3` resolves bindings without them. - Cut the next `moq-dart-v*` release with the binding breaks and confirm the workflow publishes it. - Verify the published `moq_ffi` resolves its native asset from a clean From ff3ab99e889d79f1f139e9c13de0a187f6317ef2 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 11 Nov 2026 15:37:03 -0800 Subject: [PATCH 7/7] quest: dart-publish's intro lists 0.1.1 Co-Authored-By: Claude Opus 5.5 --- quest/m3/release/dart-publish.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/quest/m3/release/dart-publish.md b/quest/m3/release/dart-publish.md index 4a57b6bde99..4c7ff3f86ee 100644 --- a/quest/m3/release/dart-publish.md +++ b/quest/m3/release/dart-publish.md @@ -9,9 +9,10 @@ A `moq-dart-v*` tag publishes `moq` to pub.dev with no manual step, as Both packages are on pub.dev (checked 2026-10-25). `moq_ffi` publishes from every `moq-ffi-v*` tag (0.4.3 through 0.4.18, the latest 2026-10-23), so its -tag-driven publish works. `moq` has only 0.1.0 (2026-09-25), the one -`moq-dart-v*` tag so far, so whether its tag publishes unattended through -trusted publishing is still unproven. +tag-driven publish works. `moq` has 0.1.0 (2026-09-25) and 0.1.1 +(2026-11-11, published by a rerun of its tag's workflow, below), so whether a +tag publishes unattended through trusted publishing, with no rerun, is still +unproven. Trusted-publishing configuration and checks of already-published artifacts can proceed independently; cutting the tag cannot.