nx_capsweep_gate.nx

nx_capsweep_gate.nx -- teeth over nx_capsweep_lib. IN-PROCESS, with every fixture assembled IN MEMORY. WHY IN-PROCESS AND WHY NO FIXTURE FILES: a gate that forks the deployed elf measures whatever artifact happens to be installed, and a gate that writes scratch under knowledge/store shares its fixture with a production beat -- the estate has measured both defects. Every function under test here is PURE over a caller-supplied buffer, so the fixtures are built in RAM, nothing is written anywhere, and a mutation reaches every rule instead of stopping at a fork boundary. THE TOOTH THAT MATTERS IS T14 and it was named by a sibling seat reviewing this organ: hide a unit that IS on the surface and assert the on-surface count FALLS. Every other tooth here proves the arithmetic is self-consistent, and a partition can reconcile perfectly while the classifier reads the wrong column. ★A RECONCILING PARTITION IS EVIDENCE THE ARITHMETIC IS CONSISTENT, NEVER THAT THE CLASSIFIER IS RIGHT.