LUTBackend.gemm and NeuralBackend.gemm materialized the full (m,n,k) product block before reducing, making peak memory cubic in layer width -- 2.4 GB for one layer's forward at the SpikeWhale panel's maximum settings. Both now block the m axis; the contraction axis k is untouched, so results are bit-identical (512x768x768: 2426.9 MB -> 77.2 MB; neural 64x96x96: 519.2 MB -> 57.5 MB).
The two backends need different block accounting: a LUT product costs 8 bytes, a neural product ~880 (four nibble pairs through a 128-wide net).
build_luts() returned its tables unchecked while the docs described a self-certify gate. The table is the complete finite domain, so certifying it IS the exhaustive verification: LUTBackend now checks all 65536 entries against signed integer multiply at construction and raises on mismatch (0.5 ms).
Exhaustive verification covered the scalar entry points; production runs the batched paths and the LUTs built from them, which are different code. test_verified_units…