From 7f0d4df85db71c6a954b42fd8fb42945164dccd6 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 7 Nov 2026 21:31:46 -0800 Subject: [PATCH 1/2] quest: clear the Mesa display and strip pan waits, narrow Apple signing's - cef-headless: a display is on nixos2's Intel port (card1-DP-1) and GNOME lists a wl_output, so the Mesa Wayland trial is agent work. - pin-audio-pan: the pan landed upstream in moq-dev/moq#8180. - signing: membership renewed and the License Agreement signed, but the notary API still reports a missing agreement. Co-Authored-By: Claude Opus 5.5 --- quest/m0/cef-headless.md | 15 +++++---------- quest/m0/pin-audio-pan.md | 15 ++++----------- quest/m0/signing.md | 29 +++++++++++++++++++---------- 3 files changed, 28 insertions(+), 31 deletions(-) diff --git a/quest/m0/cef-headless.md b/quest/m0/cef-headless.md index cfc65c8c..9d1530ac 100644 --- a/quest/m0/cef-headless.md +++ b/quest/m0/cef-headless.md @@ -52,13 +52,8 @@ Decided 2026-11-06 (maintainer, /quest-unblock): this trial runs before nixos2 switches to Windows ([windows-host](/quest/m0/windows-host.md)), which then leaves no Mesa machine on NixOS. -## Waiting - -- Maintainer: connect an HDMI dummy plug (or a monitor) to nixos2's - motherboard HDMI port, which the Intel GPU drives, since GNOME offers - Chromium no Wayland output without one. An agent cannot plug hardware, and - a virtual monitor would test a different setup from a real desktop. Check - that `cat /sys/class/drm/card1-HDMI-A-*/status` shows `connected` and that - `wayland-info` on `wayland-0` lists a `wl_output`. Alternative: skip the - Wayland trial on Mesa and let nixos2 switch to Windows, leaving the Wayland - result unknown. Recommended: the dummy plug. +Decided 2026-11-07 (maintainer, /quest-unblock): ✅ a display on the Intel +GPU's own motherboard port (rejected: one on the NVIDIA card's DisplayPort, +which tests a hybrid desktop rather than a Mesa one; skipping the Wayland +trial). It is on `card1-DP-1`, and GNOME on `wayland-0` lists a `wl_output` +named `DP-1`. diff --git a/quest/m0/pin-audio-pan.md b/quest/m0/pin-audio-pan.md index ea948fa6..3c0f538e 100644 --- a/quest/m0/pin-audio-pan.md +++ b/quest/m0/pin-audio-pan.md @@ -7,14 +7,7 @@ The `moq` submodule includes a pan on moq-audio's bus `Strip`, from ## Plan -Once the wait clears, advance it with `just upgrade-moq` in its own PR, -fixing whatever the new API breaks here. - -## Waiting - -- moq-dev/moq: the upstream quest above lands. Check: that quest's PR has - merged on moq's `main`, deleting its file, and `moq_audio::bus::Strip` - there has a pan. A quest file that moved, or went away without its work - landing, does not count. The quest itself is planned in - [moq-dev/moq#8133](https://github.com/moq-dev/moq/pull/8133), not merged - yet. +The pan landed upstream in +[moq-dev/moq#8180](https://github.com/moq-dev/moq/pull/8180) +(`Strip::set_pan` and `Strip::pan` on moq's `main`). Advance the gitlink with +`just upgrade-moq` in its own PR, fixing whatever the new API breaks here. diff --git a/quest/m0/signing.md b/quest/m0/signing.md index 1ad58031..b089fb86 100644 --- a/quest/m0/signing.md +++ b/quest/m0/signing.md @@ -18,16 +18,25 @@ Decided 2026-11-06 (maintainer, /quest-unblock): - The hang.live 1Password vault holds the Apple material for team `D7D5SDDB5Z`: `apple-developer-id` (a Developer ID Application certificate, valid until 2027-02-01), `apple-certificate` (`hang.live.p12` and its - password), and `apple-api` (an App Store Connect API key). The membership - has lapsed, so notarization fails until it is renewed. -- Once renewed, an agent with the maintainer's `op` session creates the - Developer ID profile through the App Store Connect API with that key, and - stores everything with `gh secret set` (no secret passes through chat or a - file outside `.tmp/`). Confirm the `.p12` holds the Developer ID key, not a - distribution one, before storing it. Then delete this quest. + password), and `apple-api` (an App Store Connect API key, key ID + `7WP7HJXJ4C`; its notes hold the issuer ID). +- Renewed 2026-11-07 (maintainer, /quest-unblock), and the Account Holder + signed the Apple Developer Program License Agreement that day. The API key + authenticates, but the notary API still answers + `FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED` (see `/business`). +- Once the notary API accepts the key, an agent with the maintainer's `op` + session creates the Developer ID profile through the App Store Connect API + with that key, and stores everything with `gh secret set` (no secret passes + through chat or a file outside `.tmp/`). Confirm the `.p12` holds the + Developer ID key, not a distribution one, before storing it. Then delete + this quest. ## Waiting -- Maintainer: renew the Apple Developer Program membership for team - `D7D5SDDB5Z`; only the account holder can pay. Check: `xcrun notarytool - history` with the `apple-api` key succeeds. +- Maintainer: accept any pending agreement at App Store Connect > Business + (appstoreconnect.apple.com/business), which the notary API names after the + Program License Agreement was signed; only the Account Holder can accept. + If none is pending, Apple may still be propagating the signature. Check: + `xcrun notarytool history` with the `apple-api` key succeeds (or a GET of + `https://appstoreconnect.apple.com/notary/v2/submissions` with a JWT from + that key returns 200). From 1698a956f5f2881001188f072787e1b866628cbd Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 7 Nov 2026 21:36:04 -0800 Subject: [PATCH 2/2] quest(signing): the membership renewed 2026-11-08; notary still refuses Co-Authored-By: Claude Opus 5.5 --- quest/m0/signing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/quest/m0/signing.md b/quest/m0/signing.md index b089fb86..14711968 100644 --- a/quest/m0/signing.md +++ b/quest/m0/signing.md @@ -20,9 +20,9 @@ Decided 2026-11-06 (maintainer, /quest-unblock): valid until 2027-02-01), `apple-certificate` (`hang.live.p12` and its password), and `apple-api` (an App Store Connect API key, key ID `7WP7HJXJ4C`; its notes hold the issuer ID). -- Renewed 2026-11-07 (maintainer, /quest-unblock), and the Account Holder - signed the Apple Developer Program License Agreement that day. The API key - authenticates, but the notary API still answers +- Renewed 2026-11-08, until 2027-11-08 (maintainer, /quest-unblock), after the + Account Holder signed the Apple Developer Program License Agreement. The API + key authenticates, but minutes after the renewal the notary API still answers `FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED` (see `/business`). - Once the notary API accepts the key, an agent with the maintainer's `op` session creates the Developer ID profile through the App Store Connect API