Fr0zka
8ef4d7dc09
The handoff said "No strate asset has the box ticked -- that is my call and I still haven't made it." Stale, and I reasoned from it all session. Jahni: "the data assets in game have the switch on." Everything downstream flips. The operator stack is the PRODUCTION density path, so the measured perf regression is one players feel, and any unsound EffectOverBox is a live hole rather than a latent one. The two correctness fixes committed today (7dbdf51,eaa44bf) both say "nothing in the running game was affected" in their bodies -- that sentence is wrong. Those commits are pushed and stay as written; OPSTACK-PROGRESS 2026-08-16 (h) is the correction of record. Concrete consequence:7dbdf51did not fail in practice only because this Perlin's empirical sup (~1.0-1.1) happened to stay under the margin the wrong bound left (1.27 for shafts, 1.40 for maze) -- not because the code was right. Andeaa44bfis worth checking against the real assets: if any strate has ColumnMinRadius > ColumnMaxRadius or ShaftMinRadius > ShaftMaxRadius, it WAS producing tiles with no geometry and no collision. Process failure worth keeping: the flag lives in .uasset binary data, which is not greppable from here, so the docs carried a hand-written claim about it that nobody re-checked. A fact that lives outside the repo cannot be maintained inside it -- record what it was and when it was checked, never assert it as current. Rule added to the handoff. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>