diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md deleted file mode 100644 index 8a730d5f1db..00000000000 --- a/quest/m0/ffi-shutdown-backport.md +++ /dev/null @@ -1,58 +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. - -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/m0/test-lints-hang.md b/quest/m0/test-lints-hang.md new file mode 100644 index 00000000000..94528bc34e8 --- /dev/null +++ b/quest/m0/test-lints-hang.md @@ -0,0 +1,23 @@ +# [XS] test-lints.test.py stalls just check on a busy host + +## Goal + +`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. 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 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/m2/cluster-routing/routes/playwright-pin.md b/quest/m2/cluster-routing/routes/playwright-pin.md index fd315fb268d..64d12908f2e 100644 --- a/quest/m2/cluster-routing/routes/playwright-pin.md +++ b/quest/m2/cluster-routing/routes/playwright-pin.md @@ -42,4 +42,8 @@ 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, 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..4c7ff3f86ee 100644 --- a/quest/m3/release/dart-publish.md +++ b/quest/m3/release/dart-publish.md @@ -9,15 +9,21 @@ 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. -- Confirm trusted publishing is configured for `moq` (repository - `moq-dev/moq`, tag pattern `moq-dart-v{{version}}`). +- 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 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