From 312865bffa44e19ac9a5bdfb1b3a8cd11fa69cf0 Mon Sep 17 00:00:00 2001 From: wshallwshall Date: Sat, 1 Aug 2026 09:12:18 -0500 Subject: [PATCH] fix(backlog): #320 declared no status and red main MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `test_backlog_status_check::test_the_real_backlog_satisfies_the_invariant` fails on origin/main at ea055251 itself. #320 (filed in #117) opened with a `📋 **Filed â€Ķ**` banner, which is not one of the five the invariant accepts (✅ SHIPPED / ⛔ DECLINED / ðŸŠĶ RETIRED / ðŸ”Ē Re-scored / 🚧 Status). I invented an emoji instead of using the vocabulary. It fails in 0.6s and runs in every required test leg, so it reds every PR that compiles the suite -- it was already blocking auto-merge on #119 and would have blocked #118. Corrected to `🚧 **Status: OPEN INVESTIGATION â€Ķ**`, which is what the item is, and the banner now also carries the two facts a reader needs: the measurement tooling landed in #118, and the decisive experiment is blocked on an unregistered self-hosted runner. Co-Authored-By: Claude Opus 5 --- docs/BACKLOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index 35520812..3fcaa40e 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -7298,7 +7298,7 @@ So `calling_ae_allowlist` **alone** satisfies a gate whose stated purpose is to ## 320. windows-2025 MLLP ingress is ~10x slower than a healthy runner -> 📋 **Filed 2026-08-01, not started.** Diagnosis only — the CI symptom is already fixed (#115, `06fd327d`) by widening the reconcile's stranding budget. This item is the **underlying capacity fact**, which that fix does not address and deliberately did not try to. +> 🚧 **Status: OPEN INVESTIGATION (filed 2026-08-01, not started).** Diagnosis only — the CI symptom is already fixed (#115, `06fd327d`) by widening the reconcile's stranding budget. This item is the **underlying capacity fact**, which that fix does not address and deliberately did not try to. Tooling to measure it landed in #118 (`harness/load/ingress_probe.py` + a dispatch-only sweep across ubuntu / windows-2022 / windows-2025). The decisive experiment — the same sweep on the **self-hosted WS2025 rig** — is blocked: that runner is unregistered (`actions/runners` → `total_count: 0`) and `selfhosted-win2025-sql.yml` has never run. **Type:** CI/runner capacity — not a correctness defect. No message was ever lost in any observed instance.