ci: the merge queue never gets its required check — cloudflare-pages.yml has no merge_group trigger, so every enqueued PR times out (#288 dequeued CI_TIMEOUT at 16:30Z) #298

Filing gate ① — a defect with a named landing spot and a measured reproduction. PR #288 (ready, Build and deploy green on its head bf0cf5c, auto-merge armed through the relay at 15:26Z) sat in the merge queue for an hour and was dequeued by github-merge-queue[bot] with reason CI_TIMEOUT at 2026-10-26T16:30Z. The required check Build and deploy never reported on the queue's temporary branch because .github/workflows/cloudflare-pages.yml is triggered only by push (main), pull_request and workflow_dispatch; GitHub's queue builds fire merge_group, which no workflow in this repository listens to. Business reason: with the queue on, nothing lands here through auto-merge — #288 (Developers nav, Community line, four imported posts) and #289 (three-edition pricing) are both blocked, and so is every later site PR; the maintainer merging by hand defeats the required check. Reader: the repo:www.objectos.ai seat dispatches one dev; file surface is the one workflow. Dedupe: this repository's issues searched for "merge queue merge_group CI_TIMEOUT required check" → 0 hits. Session session_01FMuBZmssbfQkVrKRtxNvng. Sibling fact: docs.objectos.ai's ci.yml already carries merge_group: and its queue landed #342 at 15:49Z.

Scope

1. .github/workflows/cloudflare-pages.yml on: gains merge_group: (no filters), so the queue build runs the same job under the same name Build and deploy — the required-check name must not change.
2. The two deploy-side steps (Create Pages project, Deploy) are gated if: github.event_name == 'push' instead of != 'pull_request', so a queue build checks and builds but never deploys; workflow_dispatch keeps deploying only if the maintainer wants it — say which in the PR (the current gate lets a manual dispatch deploy; keeping that means github.event_name == 'push' || github.event_name == 'workflow_dispatch').
3. Nothing else: no change to build, lint, SEO smoke or the Cloudflare project name.

Premises (re-check before dispatch)

• P1 — main's ruleset still requires Build and deploy and the merge queue (read the branch rules; if the maintainer has turned the queue off meanwhile, item 1 is still correct and harmless, item 2 still closes the "manual dispatch deploys" ambiguity).
• P2 — the queue's temporary branch runs the workflow file from the merge group's own commit, so this PR passes through the queue on its own change.

Acceptance

• The PR itself merges through the queue: its merge_group run reports Build and deploy and the queue merges it without a hand merge.
• After it, site: Developers nav to objectstack.ai, the ObjectOS Community line on the homepage, four framework posts imported under their original slugs #288 and site(pricing): Community · Free · Team · Enterprise — Business becomes an Enterprise contract option, Free states the MCP limits #289 re-enqueued through the relay (automerge_enable) merge the same way; the Deploy step appears only on the resulting push run.

维护者速读

你在 www 仓开了 merge queue，但部署 workflow 没有 merge_group 触发，队列分支永远等不到必需检查，#288 排了一小时后被队列以 CI_TIMEOUT 踢出。本卡给 workflow 加 merge_group: 触发，并把部署步骤限定到 push main。如果你更想直接把队列关掉，关掉后这张卡仍无害，可按需保留或关闭。