docs: prove automatic Mergify queueing after live-gate (#100)

[mast-factory]

Refs #100. Phase 4 acceptance proof after deployment PR #107; this PR alone does not complete the issue.

What changed

One line in CHANGES.md records the deployed Mergify auto-queue behavior. No workflow or configuration changes. The assigned factory/issue-100 branch was rebased onto deployed main a0ead6296ab2063e6a73a169054f0d9e1bf8d516 before this proof commit.

Exact candidate: 95eed70a5002286c1a62553a9873be78f06d9411.

Verification

Passed in builder sandbox on the candidate:

• git diff --check and staged whitespace check.
• PSTACK_STATIC_ONLY=1 bash tests/skill-collision-repro.sh: all 13 invariant groups passed.
• Node JSON.parse for all four plugin/marketplace manifests: passed.
• Diff scope: one insertion in CHANGES.md only.

Not run: Bun install/tests/strict typecheck and Claude plugin validation (Bun and Claude CLI unavailable); YAML parsing (neither yaml nor js-yaml installed). No tools were installed. Operator must run deferred checks on the exact pushed head on the Mac.

• Bun tests, strict typecheck, static invariants, and plugin validation pass (operator, Mac; see evidence).
• The exact candidate is installed in every affected harness: none affected (one CHANGES.md line).
• The changed behavior passes from its real surface: Mergify holds this PR without live-gate and auto-queues it after (recorded on Configure Mergify to auto-queue PRs once verify and Unfret pass #100).
• The installed version, action, and observed result appear below.

Live evidence:

Operator-owned proof steps

The deployment authorization is issue #100 comment 5946540669, beginning live-gate evidence: #107. PR #101 is closed as superseded.

1. Run deferred Mac checks and installed-harness testing against the exact candidate above; record results here before marking ready.
2. Mark ready; wait for verify and Unfret to pass without posting live-gate yet.
3. Capture Mergify Merge Protections / Merge Queue check summaries showing the missing live-gate hold. Run mastra-pilot's MASTRA-749 babysit-pr before the gate; it must not report MERGE_READY.
4. Post live-gate on the exact current head, immediately capture babysit-pr MERGE_READY or merged state, and observe automatic queueing and Mergify merge. Do not issue a manual queue comment on this proof PR.
5. Record the hold/queue summaries, before/after babysit-pr outputs, Mergify merger identity, two-parent merge commit, absence of a merge-queue batch branch, and absence of manual queue comments on issue Configure Mergify to auto-queue PRs once verify and Unfret pass #100 in a comment beginning live-gate evidence: proof.

If Mergify updates the head, the old exact-head gate is invalid; the operator re-tests and re-posts the gate on the new head.

A pull request without live evidence remains a draft. Builder stops after creating this draft; status posts, readiness changes, queue commands and merging are not builder actions.

[mergify]

Merge Protections

🟢 All 2 merge protections satisfied — ready to merge.

Show 2 satisfied protections

🟢 Queue ready pull requests

Automatically queue non-draft pull requests targeting main after verify, Unfret, and live-gate pass on the head.

• -draft
• check-success=Unfret
• check-success=live-gate
• check-success=verify

🟢 🚦 Auto-queue

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• -files~=^\.github/
• base = main

[ericlitman]

Operator checks on exact head 95eed70a5002286c1a62553a9873be78f06d9411 (pro14, Mac):

## operator checks on 95eed70a5002286c1a62553a9873be78f06d9411 (2026-10-02T06:18:15Z), bun 1.4.0, 2.1.283 (Claude Code)
bun install: 0
 158 pass
 0 fail
Ran 158 tests across 11 files. [18.29s]
typecheck exit: 0
manifests exit: 0
static invariants exit: 0
validate root exit: 0
validate pstack exit: 0
diff-check exit: 0

[greptile-apps]

Confidence Score: 5/5

[Low risk] Documents a change to the merge queue policy.

The one-line documentation change appears safe to merge after the PR’s stated operator proof is recorded.

What we checked:

• Workflow PRs enter the queue automatically: No. The automatic queue rule excludes PRs that change files under .github/.

Summary

Adds a change-note entry recording Mergify’s deployed auto-queue rule. It names the checks ready pull requests to main need and the operator-queueing exception for workflow changes.

• Records the required verify, Unfret, and exact-head live-gate checks.
• States that workflow changes need operator queueing.

_{Reviews (1) · Last reviewed commit: "docs: exercise deployed automatic Mergif..."}

[unfret-eal]

✅ No blocking findings

Walkthrough

This PR adds a single line to `CHANGES.md` noting that Mergify auto-queue is live. Under it, ready PRs to main need passing `verify`, `Unfret` and an exact-head `live-gate`, and workflow changes still need the operator to queue them. It makes no workflow or config changes. Its real purpose is to serve as the Phase 4 acceptance proof for #100 after deployment PR #107: Mergify should hold it until `live-gate` is posted and then queue and merge it automatically. The builder ran only static checks (diff whitespace, skill-collision invariants, manifest JSON parsing); Bun tests, typecheck, plugin validation and YAML parsing were deferred to the operator. The live-evidence section is still empty, so the checked boxes describing operator and Mergify results are not yet backed by recorded evidence, and the PR stays a draft until that is filled in.

Details

Lane / stage	Model	Effort	Outcome	Duration
broad-gpt-5.6-sol-xhigh / review	gpt-5.6-sol (reported model unavailable)	xhigh	succeeded	7 s
broad-opus-5.5-max / review	anthropic/claude-opus-5-5 (reported model unavailable)	max	succeeded	39 s
focal-gpt-6.1-sol-xhigh / review	openai/gpt-6.1-sol (reported model unavailable)	xhigh	succeeded	1 min 47 s
broad-gpt-5.6-sol-xhigh / reread	gpt-5.6-sol (reported model unavailable)	xhigh	succeeded	8 s
broad-opus-5.5-max / reread	anthropic/claude-opus-5-5 (reported model unavailable)	max	succeeded	1 min 1 s
focal-gpt-6.1-sol-xhigh / reread	openai/gpt-6.1-sol (reported model unavailable)	xhigh	succeeded	2 min 3 s

First review of this pull request.
3 reviewers finished.
Commit 95eed70.
Check run.
Run: GET /unfret/run/panel:95eed70a5002286c1a62553a9873be78f06d9411:dpW4Lnw_jVB:EZq_ezc6S5Y.

_{@unfret review · @unfret status · @unfret help}

[unfret-eal]

✅ No blocking findings
Check

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-02 06:25 UTC · Rule: default · triggered by merge protections
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-10-02 06:25 UTC · at 6c44500ab0d4708cb40b29628d099105889359c7 · merge

This pull request spent 10 seconds in the queue, including 1 second running CI.

Required conditions to merge

• github-review-approved [🛡 GitHub repository ruleset rule Protect main]
  • docs: prove automatic Mergify queueing after live-gate (#100) #108
• all of [🛡 Merge Protections rule Queue ready pull requests]:
  • -draft
    • docs: prove automatic Mergify queueing after live-gate (#100) #108
  • check-success=Unfret
  • check-success=live-gate
  • check-success=verify
• any of [🛡 GitHub repository ruleset rule Protect main]:
  • check-success = @github-actions/verify
  • check-neutral = @github-actions/verify
  • check-skipped = @github-actions/verify
• any of [🛡 GitHub repository ruleset rule Review gate]:
  • check-success = @unfret-eal/Unfret
  • check-neutral = @unfret-eal/Unfret
  • check-skipped = @unfret-eal/Unfret