<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-09-23-1-auto-merge-required-checks-gate/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-09-23-1-auto-merge-required-checks-gate/</id>
  <title>ADR: Auto-Merge Gates on the Terminal CI Aggregators — main Required Status Checks</title>
  <updated>2026-11-01T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-09-23-1-auto-merge-required-checks-gate/"/>
  <summary>main now requires the router and CI Modules terminal gates as status checks, plus repo auto-merge, so GitHub auto-merge waits for real green instead of merging on one fast check.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Ratified by the operator (agentic-framework-core-team) on 2026-09-23&lt;/strong&gt; and applied to
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; the same day. This ADR records a branch-protection
configuration decision; it changes no code. It is a sibling of
&lt;a href=&quot;/adr/3.x/2026-09-15-1-ci-main-verdict-topology/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-09-15-1-ci-main-verdict-topology&lt;/code&gt;&lt;/a&gt;
under epic &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4437&quot;&gt;#4437&lt;/a&gt; (“CI pipeline
honesty”): that ADR made a landed main tip &lt;em&gt;prove itself&lt;/em&gt; green honestly; this one makes
the &lt;em&gt;merge gate&lt;/em&gt; honour that proof before a PR lands.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s protected-branch &lt;code dir=&quot;auto&quot;&gt;required_status_checks&lt;/code&gt; listed exactly one context:
&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;Clean install verification&lt;/code&gt;&lt;/strong&gt; (a ~24s job). Because it was the only &lt;em&gt;required&lt;/em&gt; check,
GitHub treated a PR as mergeable the moment that one fast job passed — while the
architectural battery, the module-test shards, and coverage aggregation were still
running.&lt;/p&gt;
&lt;p&gt;The failure surfaced concretely when landing PR
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/pull/4953&quot;&gt;#4953&lt;/a&gt;: &lt;code dir=&quot;auto&quot;&gt;gh pr merge --rebase --auto&lt;/code&gt;
was expected to hold the PR until CI was green, but it &lt;strong&gt;merged immediately&lt;/strong&gt; with ~11
checks still pending (0 failed at the time). The merge came out clean, but only by luck of
the pending jobs subsequently passing — “merge on green” was not actually gating on green.
The same gap would let a genuinely red heavy shard land on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; if auto-merge fired
before that shard reported.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;Two settings together, both applied to &lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty&lt;/code&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;required_status_checks&lt;/code&gt;&lt;/strong&gt; is expanded from one context to &lt;strong&gt;three&lt;/strong&gt;, and
&lt;code dir=&quot;auto&quot;&gt;strict&lt;/code&gt; stays &lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt;:&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Required context&lt;/th&gt;&lt;th&gt;Producing workflow&lt;/th&gt;&lt;th&gt;Role&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Clean install verification&lt;/code&gt;&lt;/td&gt;&lt;td&gt;(kept)&lt;/td&gt;&lt;td&gt;wheel installs from a clean env&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;router gate&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;ci-router.yml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;router-gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;if: always() &amp;#x26;&amp;#x26; !cancelled()&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;the single &lt;code dir=&quot;auto&quot;&gt;gate_selection.py&lt;/code&gt; path/gate authority&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;CI Modules gate&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;ci-modules.yml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;modules-gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;if: always() &amp;#x26;&amp;#x26; !cancelled()&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;the per-module test-matrix verdict&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;allow_auto_merge: true&lt;/code&gt;&lt;/strong&gt; at the repository level. Without it &lt;code dir=&quot;auto&quot;&gt;gh pr merge --auto&lt;/code&gt;
cannot queue and silently &lt;strong&gt;degrades to an immediate merge&lt;/strong&gt; the moment a PR is nominally
mergeable — which is how a PR once merged with the heavy shards still pending.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;strict: false&lt;/code&gt; is deliberate: this repo &lt;strong&gt;rebase-merges&lt;/strong&gt;, and requiring branches to be
up to date with &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; before merging would force a re-sync churn on every PR without
adding safety the gates do not already give.&lt;/p&gt;
&lt;h2 id=&quot;rationale--why-these-three-gates-and-no-others&quot;&gt;Rationale — why these three gates, and no others&lt;/h2&gt;
&lt;p&gt;The two added contexts are the CI’s &lt;strong&gt;skipped-tolerant terminal aggregator&lt;/strong&gt; jobs. Each
runs &lt;code dir=&quot;auto&quot;&gt;if: always()&lt;/code&gt; and always posts a definitive success/failure verdict &lt;em&gt;even when its
downstream shards path-skip&lt;/em&gt; (&lt;code dir=&quot;auto&quot;&gt;ci-modules.yml&lt;/code&gt; states outright that “the required check is
the terminal &lt;code dir=&quot;auto&quot;&gt;modules-gate&lt;/code&gt;”), &lt;strong&gt;and both post their check onto the PR head.&lt;/strong&gt; That
combination — always-posted &lt;em&gt;and&lt;/em&gt; posted on the PR head — is what makes them safe to
&lt;em&gt;require&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Do not require an individual shard or a path-scoped job&lt;/strong&gt; (for example
&lt;code dir=&quot;auto&quot;&gt;architectural battery (heavy, code-scoped)&lt;/code&gt;). Those jobs are &lt;em&gt;skipped&lt;/em&gt; — never posted — on
a PR whose diff does not match their trigger paths, and a required check that is never
posted blocks the PR from merging forever.&lt;/p&gt;
&lt;h3 id=&quot;why-ci-aggregate-gate-is-deliberately-not-required-learned-by-testing-this&quot;&gt;Why &lt;code dir=&quot;auto&quot;&gt;CI Aggregate gate&lt;/code&gt; is deliberately NOT required (learned by testing this)&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;ci-aggregate.yml&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;workflow_run&lt;/code&gt;-triggered off &lt;code dir=&quot;auto&quot;&gt;CI Modules&lt;/code&gt; and therefore executes in
the &lt;strong&gt;default-branch context&lt;/strong&gt;; empirically its &lt;code dir=&quot;auto&quot;&gt;CI Aggregate gate&lt;/code&gt; check posts only onto
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; heads, &lt;strong&gt;never onto a PR head&lt;/strong&gt; (verified: 5 runs on the &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; tip, 0 on every head
of the PR that shipped this ADR, and no &lt;code dir=&quot;auto&quot;&gt;Aggregate&lt;/code&gt; context in that PR’s status rollup).
Requiring a check that never posts on a PR head puts every PR into a permanent &lt;code dir=&quot;auto&quot;&gt;BLOCKED&lt;/code&gt;
merge state — auto-merge can never satisfy it. It is a &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;-side coverage/diff-cover gate
(enforced after merge, honouring the &lt;code dir=&quot;auto&quot;&gt;2026-07-17-1&lt;/code&gt; “CI is the release authority on main”
model), not a pre-merge required check. This was caught by exercising &lt;code dir=&quot;auto&quot;&gt;--auto&lt;/code&gt; on a live PR
during the change itself; the four-gate first cut deadlocked, and the required set was
corrected to the three PR-posting gates.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;gh pr merge &amp;#x3C;N&gt; --rebase --auto&lt;/code&gt; now holds a PR until the three required gates report
success and refuses on any red — genuine on-green merging. The maintainer landing runbook
can rely on &lt;code dir=&quot;auto&quot;&gt;--auto&lt;/code&gt; for the hand-off-to-merge step instead of polling the shards by hand.
Always confirm it &lt;strong&gt;armed and did not immediate-merge&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;state: OPEN&lt;/code&gt; with a non-null
&lt;code dir=&quot;auto&quot;&gt;autoMergeRequest&lt;/code&gt; while checks pend).&lt;/li&gt;
&lt;li&gt;No contributor-facing change: this only makes the merge gate behave the way the workflow
design already intended.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rollback reference:&lt;/strong&gt; the prior state was &lt;code dir=&quot;auto&quot;&gt;required_status_checks.contexts: [&quot;Clean install verification&quot;]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;strict: false&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;allow_auto_merge: false&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;This does not alter the &lt;a href=&quot;/adr/3.x/2026-07-17-1-red-main-is-honest-ci-is-release-authority/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-07-17-1&lt;/code&gt;&lt;/a&gt;
invariant that mainline CI is the release authority; it strengthens the &lt;em&gt;pre-merge&lt;/em&gt;
application of the same honesty principle.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-01--skip-if-green-on-ready-for-review-mission-ci-runtime-stabilisation-5510&quot;&gt;Amendment (2026-10-01) — skip-if-green on ready-for-review (mission ci-runtime-stabilisation, #5510)&lt;/h2&gt;
&lt;p&gt;This amendment appends to the accepted text above and does not edit it. The set of required
contexts is unchanged: &lt;code dir=&quot;auto&quot;&gt;Clean install verification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;router gate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CI Modules gate&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;CI Aggregate gate&lt;/code&gt; stays deliberately not required. Details are in the contracts
&lt;a href=&quot;../../../kitty-specs/ci-runtime-stabilisation-01M3TZH6/contracts/green-match.md&quot;&gt;green match&lt;/a&gt;
and &lt;a href=&quot;../../../kitty-specs/ci-runtime-stabilisation-01M3TZH6/contracts/router-two-authority-amendment.md&quot;&gt;router two-authority amendment&lt;/a&gt;
(amendment A4).&lt;/p&gt;
&lt;h3 id=&quot;decision-1&quot;&gt;Decision&lt;/h3&gt;
&lt;p&gt;A required gate may now pass on matched prior-run evidence, under exactly one condition: a
&lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; run with the action &lt;code dir=&quot;auto&quot;&gt;ready_for_review&lt;/code&gt; for which a completed, successful run of
the &lt;strong&gt;same workflow&lt;/strong&gt; exists, with a non-expired marker for the identical &lt;strong&gt;tested key&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The tested key&lt;/strong&gt; is &lt;code dir=&quot;auto&quot;&gt;(workflow file, PR number, head SHA, base SHA)&lt;/code&gt;, where the base SHA is
the first parent of the merge commit the run actually tested. It is bound through the commits
API, and the second parent must equal the PR head. The &lt;code dir=&quot;auto&quot;&gt;base.sha&lt;/code&gt; the Actions API reports on a
run is not used, because it shows the PR’s current base, not the tested one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Markers.&lt;/strong&gt; Every executing &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; run uploads an artifact named
&lt;code dir=&quot;auto&quot;&gt;ci-tested-key-pr&amp;#x3C;N&gt;-base-&amp;#x3C;sha&gt;&lt;/code&gt;. A run that skipped uploads
&lt;code dir=&quot;auto&quot;&gt;ci-green-match-run-&amp;#x3C;id&gt;-attempt-&amp;#x3C;n&gt;&lt;/code&gt; and is never itself a match candidate, so skips do not
chain. Both artifacts carry the same small JSON body written by
&lt;code dir=&quot;auto&quot;&gt;scripts/ci/green_match.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;pr&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;head&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;base&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge_sha&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;run_id&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;run_attempt&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;decision&lt;/code&gt;, which is &lt;code dir=&quot;auto&quot;&gt;run&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;skip&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Effect.&lt;/strong&gt; The selection jobs of the router (&lt;code dir=&quot;auto&quot;&gt;changes&lt;/code&gt;), CI Modules (&lt;code dir=&quot;auto&quot;&gt;generate-matrix&lt;/code&gt;) and
Packs (&lt;code dir=&quot;auto&quot;&gt;changes&lt;/code&gt;) suppress their path-filter step. Every path-gated job then skips, and
&lt;code dir=&quot;auto&quot;&gt;router gate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CI Modules gate&lt;/code&gt; still post success on the PR head. This is event-level
selection-step suppression, not a third CI path routing authority: no job &lt;code dir=&quot;auto&quot;&gt;if:&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;needs:&lt;/code&gt; or
&lt;code dir=&quot;auto&quot;&gt;changes&lt;/code&gt; output expression mentions it, and &lt;code dir=&quot;auto&quot;&gt;scripts/ci/gate_selection.py&lt;/code&gt; does not model it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI Aggregate.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;collect&lt;/code&gt; runs &lt;code dir=&quot;auto&quot;&gt;scripts/ci/green_match.py effective-source&lt;/code&gt; first. When the
source run carries a skip marker, it re-points to the matched CI Modules run after re-verifying
head SHA, workflow, event, success and tested identity, and fails closed otherwise
(“re-run CI Modules to execute”). Fleet Verdict still binds by the skip run’s display title.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;never-suppressed&quot;&gt;Never suppressed&lt;/h3&gt;
&lt;p&gt;Push, &lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workflow_call&lt;/code&gt; and schedule events; any other &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; action;
any attempt after the first; a prior run that failed, was cancelled or is still in progress; a
moved base (a different tested key); a merge ref that cannot be bound to a tested key; and any
lookup error (HTTP, network, JSON or a missing key). A lookup error runs normally and emits a
&lt;code dir=&quot;auto&quot;&gt;::warning::&lt;/code&gt;. A skip marker from an earlier attempt of the same run is ignored, because markers
bind to their attempt.&lt;/p&gt;
&lt;h3 id=&quot;escape-hatch&quot;&gt;Escape hatch&lt;/h3&gt;
&lt;p&gt;Re-run the workflow. Attempt 2 always executes in full and Aggregate does not re-point.&lt;/p&gt;
&lt;h3 id=&quot;consequences-and-recorded-limits&quot;&gt;Consequences and recorded limits&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Fail-safe direction.&lt;/strong&gt; The selection step never skips on doubt, and Aggregate never passes on
doubt.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Trust surface.&lt;/strong&gt; The tested-key artifact name is written by a PR-controlled run, so on its
own it proves nothing about which PR produced it. &lt;code dir=&quot;auto&quot;&gt;decide&lt;/code&gt; binds a match in two steps, and
only the pair is trusted.
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Run identity.&lt;/em&gt; The candidate run must be the same workflow file, &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; event,
success, head SHA and repository, with the same head branch and head repository as the event
payload, and its &lt;code dir=&quot;auto&quot;&gt;pull_requests&lt;/code&gt; must list this PR. That list is not proof of authorship:
GitHub fills it live with every open PR whose head matches. A second PR from the same
branch, with a different base and a modified workflow, runs the same head SHA, head branch
and head repository and lists both PR numbers (and only this one again once it closes).&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Head uniqueness.&lt;/em&gt; Once a candidate matches, &lt;code dir=&quot;auto&quot;&gt;decide&lt;/code&gt; calls
&lt;code dir=&quot;auto&quot;&gt;GET pulls?head=&amp;#x3C;owner&gt;:&amp;#x3C;ref&gt;&amp;#x26;state=all&amp;#x26;per_page=100&lt;/code&gt; and skips only when that returns
exactly one PR, numbered this PR, with the event’s base ref and head SHA. &lt;code dir=&quot;auto&quot;&gt;state=all&lt;/code&gt; makes a
closed second PR still count. Zero, two or more, a full page (a possible second page), a
malformed entry, an unknown event base ref and any API error all run normally.&lt;/li&gt;
&lt;li&gt;Any other doubt also runs normally: empty or missing &lt;code dir=&quot;auto&quot;&gt;pull_requests&lt;/code&gt; (for example a fork
PR, which therefore always executes in full), a missing head branch or head repository, or
an unknown event-side identity.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Residual.&lt;/em&gt; The listing is a point-in-time read. A forged candidate run must already be
completed and green to be matched, so its PR exists well before the read; the only gap is
GitHub’s own propagation delay in listing a just-opened PR. The marker JSON body is still
not read: it is self-reported and proves nothing about what the run executed. CI Modules
is stronger, because Aggregate re-verifies the matched run’s identity from its immutable
merge ref.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Event guard and token.&lt;/em&gt; The &lt;code dir=&quot;auto&quot;&gt;green&lt;/code&gt; step has a step-level &lt;code dir=&quot;auto&quot;&gt;if:&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; with
action &lt;code dir=&quot;auto&quot;&gt;ready_for_review&lt;/code&gt;, so a PR that only edits the helper to print &lt;code dir=&quot;auto&quot;&gt;skip=true&lt;/code&gt; cannot skip
on any other action: the step does not run. A sibling &lt;code dir=&quot;auto&quot;&gt;green-key&lt;/code&gt; step runs the same helper on
every other &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; action solely to record the tested-key marker; nothing reads its
skip answer. The selection-job checkout also sets &lt;code dir=&quot;auto&quot;&gt;persist-credentials: false&lt;/code&gt; while PR code
runs (on push, the router keeps it because &lt;code dir=&quot;auto&quot;&gt;dorny/paths-filter&lt;/code&gt; fetches over git there).
This is not a boundary against a PR that edits the workflow file itself.&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;green&lt;/code&gt; step carries &lt;code dir=&quot;auto&quot;&gt;timeout-minutes: 3&lt;/code&gt; in all three workflows, so a stalled &lt;code dir=&quot;auto&quot;&gt;gh&lt;/code&gt;
cannot delay the run; a timeout runs normally.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recorded residuals.&lt;/strong&gt; On a skip run the always-on lanes and &lt;code dir=&quot;auto&quot;&gt;prose-scan&lt;/code&gt; still run, and
&lt;code dir=&quot;auto&quot;&gt;tests (docs)&lt;/code&gt; still runs on a prose-only skip run, because &lt;code dir=&quot;auto&quot;&gt;prose-scan&lt;/code&gt; is not suppressed.
Sonar’s informational per-change upload may repeat on a skip run. All three are accepted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Evidence caveat.&lt;/strong&gt; The Aggregate half was verified offline against recorded API fixtures
inside the mission, and live verification follows the merge, because &lt;code dir=&quot;auto&quot;&gt;workflow_run&lt;/code&gt; executes
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s copy of the workflow file.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-11-01--the-required-checks-gate-a-merge-queue&quot;&gt;Amendment (2026-11-01) — the required checks gate a merge queue&lt;/h2&gt;
&lt;p&gt;Recorded in &lt;a href=&quot;/adr/4.x/2026-11-01-1-pull-requests-touch-no-shared-generated-files-and-land-through-a-merge-queue/&quot;&gt;ADR 2026-11-01-1&lt;/a&gt;
(operator ruling of 2026-11-01).&lt;/p&gt;
&lt;h3 id=&quot;decision-2&quot;&gt;Decision&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; now merges through GitHub’s merge queue. The queue tests each PR on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; plus the PRs
ahead of it, on a temporary &lt;code dir=&quot;auto&quot;&gt;gh-readonly-queue/main/...&lt;/code&gt; ref, and rebase-merges it only when the
same three required checks pass there.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The three required checks are unchanged.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;ci-router.yml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ci-modules.yml&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; also trigger on &lt;code dir=&quot;auto&quot;&gt;merge_group&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;router gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CI Modules gate&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;Clean install verification&lt;/code&gt; report on every queue run. No other workflow joins the queue.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;strict: false&lt;/code&gt; stands.&lt;/strong&gt; The queue makes “up to date with &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;” unnecessary: it tests
the combination itself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auto-merge queues instead of merging.&lt;/strong&gt; With the queue required, &lt;code dir=&quot;auto&quot;&gt;gh pr merge &amp;#x3C;N&gt; --auto&lt;/code&gt;
adds a PR to the queue once its own checks pass. The immediate-merge degradation this ADR
guarded against cannot happen.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Skip-if-green never applies to a queue run.&lt;/strong&gt; Its steps are &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt;-only, so the queue
always runs the selected jobs on the combined commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Settings:&lt;/strong&gt; rebase merge, only non-failing PRs, build concurrency 3, group size 1 to 3,
wait time 5 minutes, status-check timeout 90 minutes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;consequences-1&quot;&gt;Consequences&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Every PR runs the required checks three times: on the PR, in the queue, and on the push to
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; that the queue’s merge makes. The queue run diffs against &lt;code dir=&quot;auto&quot;&gt;merge_group.base_sha&lt;/code&gt;, so it
stays path-scoped; the push run is the one the main-red fleet verdict reads.&lt;/li&gt;
&lt;li&gt;The queue does not resolve textual conflicts: a PR that conflicts with &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; or with a PR
ahead of it is removed from the queue and still needs a rebase.&lt;/li&gt;
&lt;li&gt;A push to a queued PR evicts it and rebuilds every group behind it.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;pr:pause-ci&lt;/code&gt; reads PR labels, which a queue run does not carry. A paused PR cannot enter the
queue (its required gates read &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;), and an already queued PR is stopped by removing it from
the queue.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
