nx_nxwreap_gate.nx

nx_nxwreap_gate.nx -- BITE-PROOF for the leaked-write-guard-scratch reaper. THE LOAD-BEARING PROPERTY IS FAIL-SAFE, AND ONE TOOTH CARRIES IT: a scratch file whose pid is still LIVE is NEVER reaped, however old. Everything else this gate asserts could be satisfied by a reaper that unlinks every file it sees -- A GUARD THAT REFUSES NOTHING PASSES EVERY POSITIVE TEST EVER WRITTEN FOR IT, which is the exact mirror of the deny-guard defect this estate has already paid for. So the live- owner fixture is the POSITIVE CONTROL: a file that MUST survive, and whose survival no count-based check can fake. THE SECOND ANTI-VACUITY TOOTH IS THE DRY RUN. Every counter this organ prints would be identical whether apply=0 wrote nothing or deleted everything, so the dry-run teeth assert THE STATE OF THE DISK, not the report. A LEAKING CALL ANSWERS IDENTICAL BYTES. FIXTURES LIVE IN /tmp/nx_nxwreap_gate AND NOWHERE ELSE. A gate that shares a fixture with a production tree measures the tree instead of the code -- and this one UNLINKS FILES, so pointing it at knowledge/ or buildroot/ would destroy real work. The directory is created at SETUP, because a teardown does not run when a run crashes, and it is PURGED at setup so the gate is idempotent: the live fixture's name contains the running pid and therefore differs on every run, so a gate that only recreated its own names would accumulate a stranger every time and lie about the count from the second run onward. THE THRESHOLD USED FOR THE FIXTURE SCANS IS PINNED HERE (NG_MAXAGE), NOT READ FROM THE CONF. A gate whose subject's behaviour moves when someone edits production config is measuring the config. The conf/default/derivation arithmetic is proved SEPARATELY, as pure teeth. license_tier: ORIGINAL expect_exit: 0