From 2c0d3ff9078cdb219943b1b44051c978998088b9 Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Thu, 20 Aug 2026 20:06:11 +0200 Subject: [PATCH] docs(lane): record that b758c2e does not build, and that its claim is withdrawn The ledger listed the merge's duplicate-SS5b defect but not the worse one: the merge commit does not compile and its message asserts that it does. Recorded with the bisect consequence spelled out, so a reader crossing that range knows why the build fails there. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai --- docs/active-work.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/active-work.md b/docs/active-work.md index e5e9960..11b6ba5 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -295,6 +295,15 @@ from #171 and #215 โ€” the correction the 1b lane missed, honoured here. and 284 GPU tests pass**. Base is no longer `72da24a`; read it with `git merge-base githubsucks/main HEAD`. - **THE MERGE CREATED ONE DEFECT AND SURFACED ONE COLLISION.** + - **Defect, fixed at `cf78385`: `b758c2e` DOES NOT COMPILE**, and its + message claims "Workspace compiles clean". **That claim is + withdrawn.** I staged the resolution, hit `cannot find value mods` + at the mapped arm, fixed it, re-checked clean โ€” and committed + without re-staging, so the verification and the commit were of + different trees. Not amended away: `b758c2e` keeps its false claim + with the withdrawal attached, because erasing a bad record is worse + than carrying a corrected one. **Anything bisecting across + `b758c2e`..`3cd7b8a` will fail to build.** - **Defect, fixed:** the merge kept BOTH copies of ยง5b โ€” this branch's stale pre-split one and main's authoritative one. I discarded the uncommitted stub edit as obsolete and missed that its