monster/HardYards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

THREADS: SPRINT10 Lane B update — browser audit built + validated, ready for site_02

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
m3ultra 2026-07-17 16:06:58 +10:00
parent 6f2990c76a
commit 9578cde8a8
1 changed files with 36 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
THREADS.md
View File

@ -3013,3 +3013,39 @@ nudge are both downstream of A's gate 1. Ready to run the instant it lands.
site_02 audit: **BLOCKED on A's gate 1** (no `data/sites/site_02_corner_block.json` on any branch yet).
Everything else on my plate is done: C answered + proven, the tool is schema-aware and safe.
---
## SPRINT10 — Lane B — 2026-07-17 (update: browser audit BUILT)
A's gate-1 `createWorld(site)` + `loadSite` landed in main mid-sprint, so I built the browser audit I
flagged above instead of waiting. **`tools/site_audit/audit.html` is the gate-2 tool now** — it does
what node can't: `createWorld(await loadSite(name))` + `dress()`, then reads the REAL dressed
`world.anchors` (GLB fascia + branch anchors, 8°-raked posts) and runs the sweep.
tools/site_audit/audit.html?site=backyard_01
tools/site_audit/audit.html?site=site_02_corner_block&storm=storm_03_southerly
Validated against backyard_01: **dressed 12/12 anchors, PASS, best line p1,p2,p3,p4 $65 + $15 spare**
— identical to the node snapshot AND to balance.test, off your real data with no snapshot anywhere.
That three-way agreement also independently re-proves your extraction is byte-identical.
The winnability math is now one file, `sweep.js`, imported by both the node and browser front-ends —
I wasn't going to ship a tool that catches reimplemented-formula drift while keeping two copies of its
own sweep. audit.mjs output is byte-identical after the refactor.
**A — two knock-ons from your merge, both handled, one worth a glance:**
1. `createWorld` now throws without a site. It crashed my tool's post cross-check (it called
`createWorld(scene,{wind})`); fixed by reading the shipped `backyard_01.json` and passing it. The
cross-check now validates the snapshot against your SHIPPED DATA — strictly better.
2. Your `balance.test.js` `buildYard` edit (site-loading) and my new fabric-hail assert crossed in
main; the rebase merged them cleanly and the whole suite is **288 green** through your
site-loading path. Your "byte-identical yard" claim is now asserted by every balance number in
the suite, since they all read the dressed yard and none moved.
**E — the tree-move offer:** the browser audit is ready, so the moment `site_02_corner_block.json`
lands I run `audit.html?site=site_02_corner_block` and post the winnable line(s) or the blocking
corner. If it's the latter, that's your cue. I can't audit the carport until it's on disk (its beam
anchors are your GLB), but the tooling is now waiting, not TODO.
**site_02 audit: still BLOCKED on the file existing** — but the wait is now one URL, not a build.