Gate 1 evidence, posted early because C's model fix and A's export are both
downstream of it.
garden_probe.html flies the sim's own garden loop (skyfx gardenExposure +
gardenHailExposure, stepped the way main.js does) per rig line and prints the
garden HP the sim would report. Browser-only by necessity: skyfx needs
`document` (node throws), so garden prediction can never live in audit.mjs.
The finding, every corner held on rated shackles (the sail's best case):
night 1 gentle no hail bare 97.6 best 99.1 sail worth +1.5
night 2 southerly 0.7 bare 83.7 best 90.1 sail worth +6.4
night 3 buster 0.7 bare 82.6 best 90.1 sail worth +7.5
night 4 wild night 1.3 bare 35.7 best 60.5 sail worth +24.8
night 5 ice night 1.4 bare 0.0 best 27.7 sail worth +27.7
The separation IS hail size, exactly as A's GARDEN_DRAIN comment predicted:
cloth blocks 100% of 1.3+ stones, 74% of pea hail, and rain at 73 degrees walks
under and does nothing. No value of GARDEN_DRAIN can separate a good rig from
none — it scales both by the same factor.
Also found: my own audit's cover% is the SUN shadow, which C's skyfx comment
already called "a number about nothing" during a storm. On the wild night it
predicts the garden BACKWARDS (r = -0.42): the best garden line is p1,p2,p3,p4
at 25% cover / $65 / 60.5 HP, beating a 71% cover / $120 line at 52.8 HP. D's
"$20 rig banked 39/45" and the QA's +$97 are the same fact — I sorted the table
by the wrong quantity.
Flagged to A: the ice night's garden cannot be saved at any price (best 27.7 vs
WIN >= 50), and night 1's sail is worth 1.5 HP.
The probe carries a TEMPORARY marked copy of main.js's private garden constants;
asked A to export the model so audit and sim share one copy. Nothing ships
against the copy — the probe is evidence, not a feature.
e839f5afe3