5 Commits

Include renames

Author	SHA1	Message	Date
Sergey Matyunin	8156f80140	fix: isolate wall union failures and guard geometry writes ... Issue: #278 User-Visible: yes	2026-08-24 08:48:37 +03:00
Sergey Matyunin	28eaf86662	fix: stabilize wall keys across storage round-trips ... Issue: #258 User-Visible: yes	2026-08-23 14:21:36 +03:00
Claude	5e95a28406	test: grade the wall-key invariant by what the product does ... The first cut of checkWallKeys compared the stored key against endpoints snapped to the lattice and called any mismatch a violation. Both halves were wrong, and measurement says so: wallIntervals reports the query key for the disputed edge as 0.887500,0.195833@1.5706, i.e. the form built from the coordinates as stored, and the two owner configurations that differ in exactly these keys produce byte-identical wall bodies and multi-wall node maps. The check would have reddened a plan that renders correctly. Graded now: a drift inside the tolerant fallback's half-pitch reach is an observation, a key beyond it or one that does not parse as coordinates is a violation. The threshold is expressed in grid steps with a 1e-3 slack — with a relative 1e-6 the four identically drifted records of one plan split between the two classes on their last bits, so the check repeated the very rounding tie it exists to expose. visual-matrix leaves KEY_CONTRACT_DEBT: its keys drift inside the reach and now read as observations. large-house stays — its labels do not parse, and wallIntervals shows all 80 solid edges resolving to zero thickness (#260). Issue: #259 User-Visible: no	2026-08-23 14:11:22 +03:00
Claude	7b267fb632	test: check the wall key against the lattice edge ... #258 lost two thickness records to a rounding tie: wallKey quantises the midpoint with Math.round, and a wall of odd step length has its midpoint exactly on the tie, where the exact node 83/240 and the stored 0.345833333 fall on opposite sides. The #254 invariants pass on that file — their edge tolerance is 0.004 and the drift is 0.00417, so the check sits on its own boundary. checkWallKeys compares strings, and against endpoints snapped to the lattice: keying from the raw endpoints flags the healthy state and passes the broken one, which is what the first formulation in #258 got wrong. Measured on the owner's before/after pair: 0 findings before, exactly the two artefact walls after. Two shipped fixtures write keys off the contract (#260); recorded as a number, so the debt can neither grow nor be silently fixed. Issue: #259 User-Visible: no	2026-08-23 13:50:37 +03:00
Matysh	5cf52707c4	test: check model invariants for references and wall records ... Issue: #254 User-Visible: no	2026-08-23 09:34:32 +03:00