[kixelated]

Completes quest/m0/waiting-sections.md: every quest here that waits on something outside the tree now lists it in a ## Waiting section, one item per condition, so quest waiting and /quest-unblock find it. The finished quest is deleted.

Changes

Reapplied 4e6fd679 (from moq-dev/quest#390) and rewrote it for the current state:

• bun-efault: oven-sh/bun: item. The Plan now names the closest existing reports, oven-sh/bun#39708, its fix oven-sh/bun#39710, and the single-file fix oven-sh/bun#38550, all open. Nobody from moq-dev has commented there yet.
• codex-project-config: openai/codex: item (openai/codex#49333, open).
• land-fixer/workflows-permission: a Maintainer: item to grant workflows: write.
• queue-watcher/follow: rind and rust2 have now landed through their queues (moq-dev/rind#276, moq-dev/rust2#467 and later), so that condition is recorded as cleared. Only a Fork contributor: item is left.
• queue-watcher/retire: moq.pro is the last repository on quest land serve, and the 2026-11-02 cutover kept it there. Its wait is a Maintainer: decision on how moq.pro leaves the gate, with options and a recommendation.
• m2/chatgpt-waitlist: a Maintainer: item (apply) and an OpenAI: item (approve).
• m2/legacy-labels: only moq.pro, rind and rust2 still pin quest from before moq-dev/quest#326.

Searching for other prose waits found three more, which the coordinator also named:

• codex-cloud-off: moq.pro's CONTRIBUTING.md still names Codex's cloud review. A second item covers stale open PRs across the repositories.
• m1/decisions-needed: open drafts still carrying ## Decisions needed on 2026-11-02 (11 in moq, 16 in moq.pro, 1 each in rind and rust2).
• gate-bench: a Maintainer: item to leave the host idle.

The link descriptions in quest/m0/README.md, quest/m0/queue-watcher/README.md and quest/m2/README.md no longer start with "condition:".

Choices made without asking

• I left quest/m0/kix/deploy.md alone, since moq-dev/quest#403 gives it a ## Waiting section. I also didn't touch quests claimed by open PRs.
• For retire's moq.pro decision I recommend checking first whether GitHub now offers a merge queue in moq.pro's ruleset editor. The other options are moving moq-dev to Enterprise Cloud, or keeping moq.pro on the gate and deleting retire. moq-dev is on GitHub Team, and moq.pro's main ruleset still requires quest land.
• gate-bench's idle host is a Maintainer: item because an agent can't pause other agents' work.

Validation

• just check passes (tsc, prettier, quest check on 89 documents, examples, worker dry-run).
• quest waiting lists every new item with its party.

Review

mechanical fix by quest land watch: merged main at 0b6fa168019b444e48050ced54a3e1d6d9196aaa with the quest merge driver (head cf3f561)

• Codex gpt-6.1-sol, medium effort, through quest review --base origin/main, round 1 on head 36f0c5fb224da81010a78c396cc5f132c66695aa: no findings.

Follow-ups

• bun-efault's report step is still undone. Its Plan already approves posting to oven-sh/bun, so the next agent on that quest should comment on #39708 or the #38550 PR with the single-file repro.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 164c2cfd-2484-41bf-a2cc-4386cd9c2bd9

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[moq-bot]

quest land watch: the merge queue removed this pull request at 36f0c5f because it conflicts with main (merge_conflict).

The land fixer works on it in the background, and the watcher re-enqueues it at the back of the queue once it is fixed or judged flaky, or hands it back here with what it needs.

(written by quest land watch)

[moq-bot]

quest land watch: armed auto-merge on this pull request at cf3f561, so it joins the back of the merge queue once its required checks pass, with main at 0b6fa16 merged in by the quest merge driver.

(written by quest land watch)