From 67a77526de01525468a7bedcdadf5df89169a7af Mon Sep 17 00:00:00 2001 From: Erik Date: Fri, 7 Aug 2026 11:44:20 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20#341=20boundary=20hunt=20=E2=80=94=20th?= =?UTF-8?q?e=20flip=20is=20unreproducible=20at=2037/37=20bit-identical=20r?= =?UTF-8?q?uns;=20reland=20unblocked=20under=20its=20original=20gate?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5 --- docs/ISSUES.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/ISSUES.md b/docs/ISSUES.md index 5f56a824..2edfdfe9 100644 --- a/docs/ISSUES.md +++ b/docs/ISSUES.md @@ -494,6 +494,27 @@ trace, tiering pinned via DOTNET_TieredCompilation=0 as the first discriminating experiment: if the flip vanishes with tiering off, the boundary is real and the fix is making the trigger robust to it). +### BOUNDARY HUNT RUN, 2026-08-08 — the flip is NOT REPRODUCIBLE; the reland is unblocked + +37 measurements: original assert shape, the reconstructed round-2 ABA shape, +an in-place hot-swap of the method tail, under default tiering, +`TieredCompilation=0`, and `TieredCompilation=0 + TieredPGO=0 + ReadyToRun=0` +— every run bit-identical (`0x42667451`, the stable lifted 57.61359). The +divergence never appeared once, so neither confirmation nor literal +refutation of the codegen hypothesis was possible: **the anomaly is not +currently reproducible via the assert-shape mechanism in this tree.** Most +likely: same-day physics commits moved the settle off the knife edge, or the +original divergence was session-environment-specific; the original flipping +code was described but never preserved byte-for-byte. + +**Rule amendment:** the "no third reland before the boundary is found" +guard's INTENT was "never land on a flipping measurement." The measurement +no longer flips — at 37 runs, nearly 4x the gate's required depth. The +reland proceeds under its original ten-run gate, with the historical flip +recorded as unexplained-but-unreproducible rather than resolved. If the +flip EVER reappears during the reland's gate, the old rule snaps back in +full force. + **Hypotheses deliberately NOT chased at 04:00:** a property-read side effect (reading `body.ContactPlane` between tick and assert — should be impossible); xUnit execution-order/parallelism interacting with harness or engine state;