kixelated · Nov 5, 2026 · Nov 5, 2026 · Nov 5, 2026 · Nov 5, 2026 · Nov 5, 2026
diff --git a/cloudflare/GITHUB.md b/cloudflare/GITHUB.md
@@ -25,8 +25,10 @@ The manifest subscribes to push, issues, issue comments, pull requests, reviews,
 review threads, inline review comments, checks and statuses. Existing App registrations
 must enable `pull_request_review_thread` and `pull_request_review_comment` in their
 webhook subscriptions so resolving discussions and replying inline wake merge jobs. GitHub also sends installation lifecycle and repository
-selection events automatically. The App also requests the **Email addresses: read**
+selection events automatically. The App also needs the **Email addresses: read**
 user permission, which Better Auth needs to sign in users whose email is private.
+GitHub rejects account permissions in a manifest, so the operator adds it in the
+App's settings after registering.
 It grants no repository authority: the user token is used only for the sign-in
 profile and email reads and to list the [project picker](#project-enrollment)'s
 repositories, and never for repository writes or authority checks. No organization,

diff --git a/cloudflare/README.md b/cloudflare/README.md
@@ -356,8 +356,8 @@ secrets. Configure the GitHub app's homepage as
 `http://localhost:8787` and callback as
 `http://localhost:8787/api/auth/callback/github`. The file is ignored by Git.
 Its `AUTH_URL` overrides the production origin in `wrangler.jsonc`. Use a
-separate GitHub App for production. The App needs the manifest's Email addresses
-read permission for accounts with private email addresses; see [GITHUB.md](GITHUB.md).
+separate GitHub App for production. The App needs the Email addresses read
+user permission, added in its settings since a manifest cannot request it, for accounts with private email addresses; see [GITHUB.md](GITHUB.md).
 
 ```sh
 just worker-dev
@@ -526,12 +526,8 @@ bun run deploy
 ```
 
 D1 schema migrations are applied separately before deployment. The `exports`
-tombstone in `wrangler.jsonc` deletes the legacy `RepositoryCoordinator`
-Durable Object namespace, and any storage it held, from Workers deployed before
-it was removed; Wrangler reports a stale tombstone where none exists. Remove the
-tombstone after the next production deploy. This does not affect the D1 auth
-database. The same `exports` block creates the SQLite-backed `RunnerHub` class
-bound as `RUNNERS`; it stores only its owner's ID, so it needs no data migration.
+block in `wrangler.jsonc` creates the SQLite-backed `RunnerHub` class bound as
+`RUNNERS`; it stores only its owner's ID, so it needs no data migration.
 
 After deploying, verify `/health`, `/setup`, and a theme asset, then complete
 sign-in/sign-out in the browser.

diff --git a/cloudflare/github-app-manifest.json b/cloudflare/github-app-manifest.json
@@ -17,8 +17,7 @@
 		"administration": "read",
 		"secrets": "read",
 		"actions": "read",
-		"environments": "read",
-		"email_addresses": "read"
+		"environments": "read"
 	},
 	"default_events": [
 		"push",

diff --git a/cloudflare/worker-configuration.d.ts b/cloudflare/worker-configuration.d.ts
@@ -1,11 +1,11 @@
 /* eslint-disable */
-// Generated by Wrangler by running `wrangler types` (hash: 551f8eb7dddde3394179c3e9fffcfd11)
+// Generated by Wrangler by running `wrangler types` (hash: 54c80306cdbeff834f3462d841b6f7b0)
 // Runtime types generated with workerd@1.20261023.1 2026-10-01 nodejs_compat
 interface __BaseEnv_Env {
 	OUTPUT: R2Bucket;
 	DB: D1Database;
 	AUTH_URL: "https://quest.moq.dev";
-	GITHUB_APP_ID: "";
+	GITHUB_APP_ID: "5622964";
 	GOOGLE_CLIENT_ID: "";
 	VAPID_PUBLIC_KEY: "";
 	ENROLL_OWNERS: [248218914,432854];

diff --git a/cloudflare/wrangler.jsonc b/cloudflare/wrangler.jsonc
@@ -15,7 +15,7 @@
 	"workers_dev": false,
 	"vars": {
 		"AUTH_URL": "https://quest.moq.dev",
-		"GITHUB_APP_ID": "",
+		"GITHUB_APP_ID": "5622964",
 		"GOOGLE_CLIENT_ID": "",
 		// The Web Push application server key; see README.md. Notifications stay off while it is empty.
 		"VAPID_PUBLIC_KEY": "",
@@ -54,8 +54,5 @@
 	"durable_objects": { "bindings": [{ "name": "RUNNERS", "class_name": "RunnerHub" }] },
 	"exports": {
 		"RunnerHub": { "type": "durable-object", "storage": "sqlite" },
-		// Deletes the legacy RepositoryCoordinator namespace and its storage if an earlier deploy
-		// provisioned it; a no-op otherwise. Remove this tombstone once every deploy has applied it.
-		"RepositoryCoordinator": { "type": "durable-object", "state": "deleted" },
 	},
 }
diff --git a/quest/m0/README.md b/quest/m0/README.md
@@ -92,16 +92,13 @@ ownership-manifest design:
 
 - [Land through the merge queue with an async fixer](/quest/m0/queue-watcher/README.md) - GitHub's merge queue lands one PR at a time, and a host watcher fixes and re-enqueues each PR it drops
 - [Merge through a host gate](/quest/m0/host-land/README.md) - the host's fixer containers, and the frozen batched gate for the repositories not yet switched, with merge-commit landing as its one exception
-- [The land fixer resolves every mechanical failure](/quest/m0/land-fixer/README.md) - workflow pushes and the PR's own CI as context
+- [The land fixer resolves every mechanical failure](/quest/m0/land-fixer/README.md) - the docs listing what the fixer resolves and hands back
 - [Review sessions keyed by upstream branch](/quest/m0/review-session-key.md) - a round from a local branch tracking the PR branch continues that branch's review session
 - [Kix decision UI](/quest/m0/kix/README.md) - planning and implementation through prompts and summaries, run on the maintainer's own runners
 - [Route quests to models by size](/quest/m0/model-routing/README.md) - `/quest-spawn` starts each quest on the first model of its size's ranked list that can run, reviews rank the same way, and PRs record size, implementer, and reviewer
 - [Model check](/quest/m0/model-check.md) - recurring: the first audit of the routed PRs retunes the built-in size lists
 - [Codex cloud off](/quest/m0/codex-cloud-off.md) - automatic Codex cloud reviews stop once no open PR relies on them
 - [Codex project-config skip](/quest/m0/codex-project-config.md) - once Codex keeps a supported way to skip a project's `.codex/` layer, reviews keep the user's config
-- [Gate bench](/quest/m0/gate-bench.md) - measure headroom admission on an idle host
-- [Agent workflow helpers](/quest/m0/helpers/README.md) - CLI commands for CI waits, PR status, claims, quest moves, and serialized merges
 - [Agents get the dev shell from user settings](/quest/m0/user-dev-shell/README.md) - maintainers' own Claude and Codex settings load the dev shell; repositories drop dev-shell hooks, Quest worktree hooks, and `nix develop` instructions, and `quest init` writes no hooks
-- [Remote control worktrees](/quest/m0/worktree-routes.md) - live-check `claude remote-control --spawn worktree` against the hooks, from a session spawned on claude.ai
 - [Session checkouts released](/quest/m0/session-checkouts.md) - a Claude session's own checkout is released when the session ends and reclaimed on resume
-- [claude rm upstream report](/quest/m0/claude-rm-upstream.md) - waiting on approval: ask Claude Code to run `WorktreeRemove` instead of advising an unlock
+- [claude rm upstream report](/quest/m0/claude-rm-upstream.md) - posting approved: ask Claude Code to run `WorktreeRemove` instead of advising an unlock
diff --git a/quest/m0/claude-rm-upstream.md b/quest/m0/claude-rm-upstream.md
@@ -14,6 +14,14 @@ Decided 2026-11-02 (coordinator, /quest-spawn follow-ups, after the user
 asked the coordinator to decide follow-ups from evidence): plan it, [XS],
 m0, waiting on the maintainer's approval to post.
 
+Decided 2026-11-04 (maintainer, /quest-unblock): posting on
+anthropics/claude-code is approved.
+
+- Can I file the issue on anthropics/claude-code?
+  - ✅ Approve posting
+  - Decline
+  - Skip for now
+
 - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425)'s probe
   with Claude Code 2.1.316: `claude rm` on an agent-view session's
   hook-made checkout reports it "locked … by something other than Claude
@@ -28,7 +36,3 @@ m0, waiting on the maintainer's approval to post.
   them in the report.
 - Include the Claude Code version, the minimal reproduction from #425's
   scratch repository, and the expected behaviour.
-
-## Waiting
-
-- Maintainer: approve posting on anthropics/claude-code, which is outside the kixelated and moq-dev orgs where agents may post without asking; check by a ✅ recorded in this quest's Plan
diff --git a/quest/m0/gate-bench.md b/quest/m0/gate-bench.md
diff --git a/quest/m0/helpers/README.md b/quest/m0/helpers/README.md
diff --git a/quest/m0/helpers/headless-agents.md b/quest/m0/helpers/headless-agents.md
diff --git a/quest/m0/kix/README.md b/quest/m0/kix/README.md
@@ -139,7 +139,6 @@ fixes what it finds:
 
 ## Required
 
-- [Deploy quest.moq.dev](/quest/m0/kix/deploy.md) - the operator registers the App and deploys the Worker with GitHub sign-in at quest.moq.dev
 - [Operator setup](/quest/m0/kix/operator-setup.md) - pilot installations and a verified test PR on moq-dev/moq and moq-dev/quest
 - [Private repositories](/quest/m0/kix/private.md) - moq-dev/moq.pro enrolls, visible only to signed-in users who can read it
 - [Job sandbox](/quest/m0/kix/sandbox/README.md) - head approval for kix-pushed heads, and opencode sandboxed