the published reading is builds, and mine was runs

CI measured mimalloc's Windows cell as `builds`: the backend crash is gone and
the member compiles and links, and its `alloc` test then exits 1 under the Wine
that CI installs while passing under the one on this machine. The recipe
comment claimed `runs` on the strength of the local run.

The build repair stands — the cell was `fails: error: build failed` — but a
repaired build is not a passing test, and both the recipe and docs now say
which one this is. The sixty-cell table is CI's, not mine: 56 runs, 1 builds,
3 fails, all three declared.

Author: Sunrisepeak

docs/openkal-compat.md

@@ -167,6 +167,25 @@ lower. The comparison becomes a required check for pull requests once the
 repository variable `OPENKAL_RATCHET` is `on`; it is enabled after the weekly
 measurement has been stable for two consecutive weeks.
 
+### The 2026-09-21 measurement, on mcpp 2026.9.21.3
+
+Thirty members, two targets, sixty cells, measured by this repository's own CI:
+
+| | before | after |
+| --- | --- | --- |
+| `runs` | 50 | **56** |
+| `builds` | 0 | 1 |
+| `fails` | 10 | **3, all declared** |
+
+`compat.py check` against the published baseline: no published label
+regressed, and no declaration was contradicted.
+
+The one `builds` is `mimalloc` on `x86_64-windows-gnu`. Its build was repaired
+in this round — `MI_USE_BUILTIN_THREAD_POINTER=0`, see the recipe — and its
+`alloc` test then exits 1 under the Wine CI installs while passing under
+another. A repaired build is not a passing test, and the label says which one
+this is.
+
 ### Why `aarch64-macos` is not a pinned target yet
 
 `pins.toml` names linux and windows. macOS is measurable — `mcpp test --no-run`

pkgs/c/compat.mimalloc.lua

@@ -135,6 +135,16 @@ package = {
             -- Windows branch, and on a Win32 target the setting is not read at
             -- all --- `_WIN32` selects `NtCurrentTeb()` three arms earlier ---
             -- so it changes only the target that has no `_WIN32`.
+            --
+            -- WHAT THIS FIXES AND WHAT IT DOES NOT. The cell goes from
+            -- `fails: error: build failed` to `builds`: the backend crash is
+            -- gone and the member compiles and links for this target. Its
+            -- `alloc` test then passes under one Wine and exits 1 under the
+            -- one this repository's CI installs, so the published reading is
+            -- `builds` rather than `runs`. That remainder is a separate
+            -- question about the TLS path the override falls back to, and it
+            -- is recorded here rather than folded into this one so the next
+            -- reader does not take a green build for a green test.
             cflags = { "-DMI_USE_BUILTIN_THREAD_POINTER=0" },
         },
     },