nx_rigfloor_gate.nx

nx_rigfloor_gate.nx -- THE GATE FOR THE DERIVED ASSET FLOOR. SUBJECT: the nx_rigfloor ELF, forked for real. The organ's whole contract is its FOUR-STATE EXIT (0 OK / 1 OUT-OF-BAND / 2 usage / 3 UNOBSERVABLE), and /api/gate_run derives its verdict from an exit code, so a gate that inspected only stdout would test the least load-bearing half. Every tooth here asserts an EXIT CODE, and the content teeth additionally read the conf that was actually written. FIXTURES ARE ASSEMBLED AT RUNTIME, IN /tmp/nx_rigfloor_gate/. Two reasons, both measured in this estate: a detector that scans source will find its own test fixture (writing the pattern in a COMMENT re-arms the trap), and a gate that shares scratch with a production beat reports on the FIXTURE rather than the code -- segguard folded a real store mid-run and the gate blamed the subject. Scratch is created by sys_mkdir at SETUP, because a teardown does not run when a run crashes. THE ANTI-VACUITY TOOTH IS T2, AND IT IS THE POINT. T1 only proves the organ exited 0. A floor organ that wrote a hardcoded conf and exited 0 would pass T1 forever. T2 asserts the fixture REACHED THE CONDITION (n_read equals the rows the roster declared) and T3 asserts the emitted band actually SPANS the fixture values -- i.e. that the number was MEASURED, not emitted. A green here without T2/T3 would be the gates-green-on-garbage class. THE NEGATIVE CONTROL IS T5, PAIRED WITH T4 THROUGH gv_bite: an asset inside the band must score IN-BAND and an asset outside it must score OUT-OF-BAND. A guard that refuses everything passes every deny-test, so the ALLOW case is not decoration -- it is the half that catches it. license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0