nx_langspec_gate.nx

nx_langspec_gate.nx -- THE REFEREE for lang.plan rung LR5 (written specification plus conformance suite, watch symbol spec_conformance_run). THE ROW NAMES ONE TOOTH AND THIS GATE IS BUILT AROUND IT: "a planted deviation goes RED". A conformance runner that cannot fail is a certification costume, so the load-bearing question is not whether the suite passes -- it is whether the runner would NOTICE if the compiler stopped obeying the specification. That is asserted here by PLANTING a divergence between a written clause and the shipped compiler and requiring the runner to report DEVIATION and name the case. FIXTURES ARE ASSEMBLED AT RUNTIME into /tmp/nx_langspec_gate/, never committed beside the organ: a gate that shares a fixture with a production beat measures the fixture, and a detector that scans source finds its own fixture. The fixture spec, its three suites and its OWN conf are written here by this gate on every run, so the gate carries its own thresholds and never has to lower the live coverage ratchet to make its fixtures pass -- lowering the production floor to fit a test is editing the detector to flatter the measurement. WHY A SEPARATE CONF FIXTURE MATTERS. The production ratchet stands at full coverage. A fixture spec deliberately carries one clause NO case exercises, because the unexercised list is the rung's real deliverable and a list that is always empty cannot be shown to work. Its own conf sets a floor the fixture meets, so the two facts stay independent. SUBJECT: the SHIPPED runner (nx_langspec.elf, resolved from the cwd or from _offc/), driving the SHIPPED compiler. Nothing here simulates either. The absent-compiler control proves it: point the runner at a compiler that does not exist and it must ABSTAIN, not acquit and not convict. exit: gv_verdict (0 GREEN / 1 RED / 3 SKIP). license_tier: ORIGINAL. No hw writes (Rule 26).