From fd85bcd2545e277327206a7df6d6a1d22c6af25c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sun, 8 Nov 2026 08:56:00 -0800 Subject: [PATCH] quest: track deletion of the retired kixel-quest App Co-Authored-By: GPT-6 Astra --- quest/m0/README.md | 5 +++-- quest/m0/delete-kixel-quest-app.md | 30 ++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+), 2 deletions(-) create mode 100644 quest/m0/delete-kixel-quest-app.md diff --git a/quest/m0/README.md b/quest/m0/README.md index 76546c3c..d1675a4a 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -16,8 +16,9 @@ launch belong to [m1](/quest/m1/README.md). Decided 2026-11-08 (user): Quest serves moq-dev only, so kix goes. Its Worker at quest.moq.dev, `quest runner`, the `quest:kix` hold, kix's -sessions comment, and its GitHub App, kixel-quest, are deleted, along with -the quests that built on them. moq-bot is the only GitHub App. +sessions comment, and the quests that built on them are deleted. Deleting +its GitHub App, kixel-quest, still waits on authenticated browser access. +moq-bot is the only GitHub App used by the host's daemons. - Does kix go, or only its App? - ✅ Delete kix entirely (recommended): it had never run on a real diff --git a/quest/m0/delete-kixel-quest-app.md b/quest/m0/delete-kixel-quest-app.md new file mode 100644 index 00000000..7a037fb2 --- /dev/null +++ b/quest/m0/delete-kixel-quest-app.md @@ -0,0 +1,30 @@ +# [XS] Delete the retired kixel-quest GitHub App + +## Goal + +The moq-dev-owned kixel-quest GitHub App (ID 5622964) is deleted, completing +kix's retirement. moq-bot remains the App used by the host's daemons. + +## Plan + +Decided 2026-11-08 (user): record the remaining App deletion as a follow-up +after browser automation could not connect. This belongs to m0's existing +decision to retire kix. + +[moq-dev/quest#575](https://github.com/moq-dev/quest/pull/575) removed kix's +code. The quest-cloudflare Worker, quest-auth D1 database, and quest-output +R2 bucket were subsequently deleted; quest.moq.dev no longer resolved at +handoff. Only the GitHub App deletion remains. + +In [moq-dev's GitHub App settings](https://github.com/organizations/moq-dev/settings/apps), +open kixel-quest, verify its App ID, and use Advanced to delete it. An agent +can drive the authenticated browser once access works. Verify the App is +absent from the organization's owned Apps, then remove this quest. + +## Waiting + +- Maintainer: reconnect an authenticated Chrome session for agent control, + or delete the App directly. The Chrome MCP repeatedly returned "The browser + access host is unavailable"; the T3 browser reached GitHub's sign-in page. + No API deletion route was identified. Clear this wait when browser access + works or the App's absence is verified in moq-dev's owned Apps.