From d28b00b690e127d423e17c37b8e1878ee778095d Mon Sep 17 00:00:00 2001
From: dondonz <13839920+dondonz@users.noreply.github.com>
Date: Sat, 14 Mar 2026 16:05:04 +1100
Subject: [PATCH] Remove coverage gate checks from the CI doctor because it's
 spammy

---
 .github/workflows/ci-doctor.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/ci-doctor.md b/.github/workflows/ci-doctor.md
index d2499e3af..e26a9f385 100644
--- a/.github/workflows/ci-doctor.md
+++ b/.github/workflows/ci-doctor.md
@@ -50,6 +50,7 @@ You are the CI Failure Doctor, an expert investigative agent that analyzes faile
 1. **Verify Failure**: Check that `${{ github.event.workflow_run.conclusion }}` is `failure` or `cancelled`
 2. **Get Workflow Details**: Use `get_workflow_run` to get full details of the failed run
 3. **List Jobs**: Use `list_workflow_jobs` to identify which specific jobs failed
+4. **Check for Excluded Failures**: If the only failed jobs are coverage-related (e.g., "Per-Class Coverage Gate"), exit immediately without creating an issue or comment
 
 ### Phase 2: Log Analysis
 
@@ -97,6 +98,10 @@ When creating an investigation issue, use this structure:
 - [ ] [Specific actionable steps with file paths and line numbers]
 ```
 
+## Excluded Failure Types
+
+- **Coverage Gate Failures**: If the only failures are from the "Per-Class Coverage Gate" job or coverage-related checks (e.g., coverage regressions, JaCoCo threshold violations), do NOT create an issue or comment. These are intentional quality gates that developers handle themselves. Exit without reporting.
+
 ## Important Guidelines
 
 - **Build Output Only**: Base your analysis solely on the job logs — do not search issues, PRs, or external sources