[Cuarroc]

Die Anleitung behauptete, fertige PRs kämen von selbst in die Mergify-Warteschlange – in der Praxis hat der Koordinator jeden PR mit dem Kommentar @Mergifyio queue eingereiht. AGENTS.md und docs/setup/mergify.md beschreiben diesen Schritt jetzt ausdrücklich; warum die automatische Aufnahme nicht greift, bleibt offen. Es ist reine Doku: an der Queue, an Labels, am Mergify-Konto und an PRs ändert sich nichts.

Report

Package: documentation correction, Mergify explicit enqueue (not an M package, no spec file). Branch claude/mergify-explicit-enqueue, head 70ad850a11840c465e8a4d79a13fbd8843f927e6, branch point 7ea73b2; current PR base 4846c84 (three main commits newer).

What changed

• AGENTS.md ("Merging"): the PR conditions (non-draft, required checks green, no conflict, no do-not-merge) are now described as eligibility, not as automatic queueing. Added the explicit step: when gh pr checks <n> is green, the coordinator comments @Mergifyio queue. The cause is marked unresolved (hypotheses only); Mergify still checks the queue run on main.
• docs/setup/mergify.md: same correction in German ("Aufnahmefähig" + "Einreihen ist ein eigener Schritt", observation date 04.10.2026, gh pr comment <n> --body "@Mergifyio queue"), plus item 7 in "Warum steht mein PR nicht in der Queue?".
• No change to .mergify.yml, branch protection, labels, Mergify account/dashboard or other PRs.
• Diff: 2 files, +25/-8.

Evidence (2026-10-04)

• Queue comments: gh pr view <n> --json comments with the filter @[Mm]ergify(io)? (queue|requeue). A checked set of 14 merged PRs (test(hygiene): accept a PLAN with zero in-progress packages #240, docs(plan): sync package status with merged PRs, keep E13 (PLAN-STATUS-03) #242, refactor(settings): extract UpdatesTab from SettingsView (ARCH-08d) #244, refactor(api): move goal routes into hq_routes (ARCH-10c) #246, refactor(settings): extract CategoriesPanel from SettingsView (ARCH-08e) #247, refactor(api): move task and control routes into hq_routes (ARCH-10d) #250, docs: state HQ proof boundaries for W3-08 and consumers #251, refactor(settings): extract ProfilesPanel (ARCH-08f) #252, Share the Windows replace primitive with DB restore (ARCH-03c) #256, docs: reconcile PLAN, STAND and KNOWN_ISSUES with live PR state #258, refactor(ipc): move project wrappers into ipc/projects.ts (ARCH-09a) #260, test: show drain unresolved ids and completion results in assertion message #262, refactor(ipc): move worker wrappers into ipc/workers.ts (ARCH-09b) #264, docs: sync PLAN, STAND and KI-30 to main cc95a57 #266) each has at least one match; fix(hq): ein 'teilweise:'-Paket in der Stand-Spalte nicht als fertig zählen (W1-17) #274 and docs(setup-15): correct provider, routing and script references in docs/setup #275 also have queue/requeue comments. Spot check test(hygiene): accept a PLAN with zero in-progress packages #240/docs: sync PLAN, STAND and KI-30 to main cc95a57 #266/docs(setup-15): correct provider, routing and script references in docs/setup #275: the comment @Mergifyio queue is by Cuarroc (coordinator), followed by a Mergify bot reply (docs(setup-15): correct provider, routing and script references in docs/setup #275: no reply yet).
• npm run dev:start-check -- --json before the gates: exit 0 (3.9 GB free RAM, 0 cargo builds; provider limit not checked by the script, coordinator observed Claude 35 % for the week).
• Secret scan on the staged diff: bash scripts/ci/secret-scan.sh exit 0, no leaks.
• bash scripts/ci/gates.sh lane prepush in this worktree on 70ad850: exit 0, 427 s, all 11 gates green (rust-suite 191 s). A first attempt failed typecheck (TS2688) because the new worktree had no node_modules; fixed with npm ci from the lockfile, no repo change.
• Push: git ls-remote origin refs/heads/claude/mergify-explicit-enqueue = 70ad850a11840c465e8a4d79a13fbd8843f927e6.
• lane-plan.sh --classify: AGENTS.md heavy (gates read it literally), docs/setup/mergify.md light, so the linux lane runs on this PR.

Test trailer

No-Test: documentation-only correction; no runtime effect.

Review disposition

Tier C (documentation without runtime effect): no external review; the gates are enough (AGENTS.md rule 5).

NICHT ABGEDECKT

• Why Mergify does not pick up eligible PRs on its own: not investigated, recorded as unresolved. Not verified against the Mergify dashboard or account settings (deliberately left alone).
• Only the Windows half was run locally; the Linux half comes from CI (KI-7).
• The PR evidence is a snapshot from 2026-10-04; older PRs before test(hygiene): accept a PLAN with zero in-progress packages #240 were not checked.
• Other docs that may still say "queued automatically" (outside the two files in scope) were not searched or changed.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-04T09:44:05.477952Z	70ad850	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 70ad850a11

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Verify manual queueing before making it mandatory

The presence of queue comments proves only that coordinators posted them, not that eligible PRs would otherwise remain unqueued. This is especially important because the declared source of truth, .mergify.yml, still configures matching merge_protections_settings.auto_merge_conditions, which Mergify documents as automatically adding matching PRs to the queue. Confirm the behavior with an eligible PR left uncommented or with the Mergify account/dashboard state before documenting a mandatory human step; otherwise this introduces an unnecessary manual gate based on an unsupported causal claim.

AGENTS.md reference: AGENTS.md:L40-L41

Useful? React with 👍 / 👎.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[Cuarroc]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-04 09:49 UTC · Rule: default · triggered by @Cuarroc with the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: checking #279 on main (f33f40d) #280
• ✅ Merged — 2026-10-04 10:03 UTC · at effef1acdd8b845618cb4bb5580d20d93b271d2a · merge

This pull request spent 13 minutes 33 seconds in the queue, including 13 minutes 18 seconds running CI.

Required conditions to merge

• check-success = gates (linux)
• check-success = gates (windows)
• check-success = red-first
• label != do-not-merge
  • docs(mergify): enqueue eligible PRs explicitly with @Mergifyio queue #279