Skip to content

quest: track deletion of the retired kixel-quest App #578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kixelated wants to merge 1 commit into
base: main
Choose a base branch
from
+33 −2
Open

quest: track deletion of the retired kixel-quest App #578

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions quest/m0/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
30 changes: 30 additions & 0 deletions quest/m0/delete-kixel-quest-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.