nx_wasmfit.nx

nx_wasmfit.nx -- THE ONE RULER FOR "CAN THIS MODULE'S FRAMEBUFFER EXIST IN THE MEMORY IT DECLARES". WHY IT IS A LIBRARY AND NOT A CHECK INSIDE AN EMITTER. On 2026-08-14 /craft shipped BLACK TWICE: its framebuffer had outgrown the module's own declared linear memory (needed 22,022,528 bytes against 192 pages = 12,582,912), so every browser frame trapped with "index out of bounds". The guard that now refuses that was written INSIDE nx_game_page_emit's gpe_build_s, whose header claimed "every wasm page in the estate is built through this function -- one guard here covers all of them". THAT CLAIM WAS FALSE, AND MEASURED SO ON 2026-08-15. nx_wasmpage_census walked all 62,906 shipped html pages: 25 carry an embedded wasm module, and only 9 come from gpe_build_s. The other 16 -- pong, racing, td, city, shmup, explorer, adventure, voxelworld, sudoku and the rest -- are emitted by organs that each hand-pasted their own copy of the same blit shim and none of the guard. ★★★★★★A GUARD PLACED IN "THE" SHARED PATH IS ONLY AS BROAD AS THE CLAIM THAT THE PATH IS SHARED, AND THAT CLAIM IS A MEASUREMENT NOBODY TOOK. The census took it and the answer was 9 of 25. So the ruler moves DOWN here, where any emitter can reach it, and gpe_build_s becomes one of its callers rather than its owner. ★EXTEND THE INCUMBENT, NEVER ADD A SECOND RULER: the arithmetic below is gpe_build_s's, moved rather than re-typed, so there is exactly one definition of "fits" in the estate and no opportunity for two of them to drift. It asks the ARTIFACT, never a constant typed in another file: wm_parse reads the module's own memory section, and fb_off/ww/hh are the module's own accessors. With no init() the quality slot is zero, which clamps to the FINEST setting, so ww/hh report the worst case the adaptive controller can ever reach -- exactly the case that has to fit. Cheap by construction: three accessor calls and no render, so it costs nothing per emit and there is no reason for any caller to skip it. license_tier: ORIGINAL