From 673a06dab8d153447786c7a05e3da153bf310ca3 Mon Sep 17 00:00:00 2001 From: type-two Date: Fri, 17 Jul 2026 18:26:21 +1000 Subject: [PATCH] [data] round 3 notes addendum: retune fixed two UI heat tests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Measured after LANE-UI landed live.test.ts: their THROTTLING/SCRAM HUD tests fail on round-2 data and pass on round 3 (heat was decorative before). Their remaining anchor-slab failure is independent of data — fails identically either side of the retune; likely the reference layout circulating recovered slabs back into the assembler instead of an uplink. Co-Authored-By: Claude Opus 4.8 --- fktry/lanes/LANE-DATA.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/fktry/lanes/LANE-DATA.md b/fktry/lanes/LANE-DATA.md index e2752d5..5fb3642 100644 --- a/fktry/lanes/LANE-DATA.md +++ b/fktry/lanes/LANE-DATA.md @@ -290,3 +290,28 @@ forward-canon commission that's blocked on data rather than mechanics); the ASIC aura the round SIM has auras; a seam/ore map — SIM notes extractors currently mine anywhere because `data/` has no seam data, which is a real content gap I own; `cinema-pack` + the Fortress when M4 lands. + +POST-PUSH ADDENDUM (same round, after LANE-UI landed `src/ui/live.test.ts`): + +- **My retune fixed two of UI's tests.** Their HUD tests "shows heat climbing, then + THROTTLING, then SCRAM" and "keeps reading SCRAM from the latch while the unit cools" + both FAIL against round-2 data and PASS against round 3 — they could never have passed + while heat was decorative. Measured by restoring the old JSON and re-running. +- **UI: your remaining failure is not data.** `ships, tickers up, and raises the + SANITISING chip on real anchor-slab shipments` fails identically before *and* after my + retune (`expected -1 to be greater than 0` — no anchor slab ever reaches an uplink). + Worth checking whether the reference factory routes recovered slabs back into the GOP + assembler rather than to an uplink: `mosh` hands its winched-out slab straight back, and + `assemble-gop` consumes one per crate, so a closed loop will happily circulate every + slab forever and ship none. That's a layout question, not a recipe one — the ratio is + 1 slab in, 1 slab out, by design (§4: "recoverable — sell it!"). + +- **PROCESS — the shared git index bit us again, in reverse.** Last round my `git add` + swept up UI's staged deletion. This round LANE-SCREEN's commit `4803b6a` swept up *my* + staged `git mv` of the validator, so the ordered file move is recorded under + `[screen] signal strain` instead of `[data]`. Already pushed and shared by five + sessions, so I left history alone — the tree is correct, only the attribution is wrong; + a force-push to fix a commit message would be far more damaging than the wart. + **Five sessions share one index: `git add ` does not isolate a lane.** Suggest a + standing rule — every lane runs `git diff --cached --name-only` before every commit and + unstages anything outside its owned paths.