The "a sampler must cover at least one period" bug was found in the tunnel test
(+/-32 vs RoomSpacing 80) and again in the shaft test (+/-48 vs ShaftSpacing 55).
Both were fixed. The class was not: three box-verdict scans still ran the
original RandRange(-6,6)*Extent at Step 1 / Cells 8, i.e. +/-48 voxels.
Island +/-48 vs IslandSpacing 95 = 0.51 periods (worse than either fix)
Slab +/-48 vs ColumnSpacing 60 = 0.80 periods
Maze +/-48 vs CellSize 40 = 1.20 periods
Verified the fixture does not override any of those spacings, so the header
defaults are what these tests really ran against.
This matters now specifically: 7dbdf51 changed the island and maze verdicts and
eaa44bf changed the slab column verdict, and these are the tests that guard
them. Widening before the build is what makes that build's green mean anything.
The rule the fixed tests already encoded, now explicit: Extent = 8, so
SpanCells = the lattice spacing gives exactly 8 periods -- which is where the
shaft test's 55 came from. Island 95, Slab 60, Maze 40, each printing the ratio
computed LIVE from the params struct so a future narrowing cannot be silent.
No assertion, tolerance, AddError, brute-force loop, seed, Step, Cells or tile
count was touched: this changes what the measurement looks at, never what it
demands. Proved counts will move (expected); NumUnsound must stay 0.
Test-only -- git diff lists three files under Private/Tests/. Not built.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Fr0zka
f737488d88