From 2a9e23f72fb3656077c65563f8f32b07aa44e070 Mon Sep 17 00:00:00 2001
From: Matt Evans <1388610+matthewevans@users.noreply.github.com>
Date: Tue, 9 Jun 2026 21:55:48 -0700
Subject: [PATCH] ci: make coverage ratchet informational on push-to-main
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On push-to-main the regression check can only do harm: the merge has
already happened, and a failing check blocks the R2 baseline republish
that runs later in the same job — wedging main red until someone
manually uploads a baseline (the recurring PR #2339 / PR #2802
swallowed-clause ratchet deadlock). continue-on-error on main pushes
lets the baseline self-heal after an intentional ratchet absorption,
while PR and merge_group runs remain fully blocking.
---
 .github/workflows/ci.yml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 9e03deb1c0..14195750c1 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -171,6 +171,11 @@ jobs:
         # the engine now lacks a handler (non-ParseWarning gap). Parser-honesty
         # flips (new ParseWarning:*) and genuinely-gained cards are informational.
         # Baseline is main's last-good coverage-data.json published to R2.
+        # On push-to-main the check is informational only: the merge has already
+        # happened, and failing here blocks the R2 baseline republish below,
+        # wedging main red until a manual baseline upload (the PR #2339 /
+        # PR #2802 ratchet deadlock). PR and merge_group runs remain blocking.
+        continue-on-error: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
         run: |
           ./scripts/coverage-regression-check.sh \
             "https://pub-fc5b5c2c6e774356ae3e730bb0326394.r2.dev/preview/coverage-data.json" \