nx_builddeploy_gate.nx

nx_builddeploy_gate.nx -- holds nx_builddeploy_lib, THE ruler for "may this build write a consumer-visible binary?". IN-PROCESS by construction: the lib is pure integer logic in this gate's own build closure, so nx_gate_bite can actually reach it. A gate that fork/execs a deployed elf cannot be mutation-proven (every mutant reads NOT-REACHED), which is precisely why the queued-build class went unmeasured -- the decision lived inline in a 105KB builder that no fixture could drive. THE DEFECT THIS EXISTS TO STOP, measured 2026-08-26 from the queue's own artifact: [nx_sov_build_run] nx_gate_roster_run: DEPLOYED to serving root (twin refresh, live for the next fork) -> ../nx_gate_roster_run.elf seeded by /api/build's load-refusal path, which had told the caller only that the build was deferred and to "promote deliberately afterwards". THE TWO TEETH THAT MATTER ARE A PAIR, AND EITHER ALONE IS A TRAP: - build-only must install NOTHING (stops the defect) - the DEFAULT path must still refresh a present twin (stops the over-correction) A fix that silenced the first by disabling all installs would reintroduce LM-026 staleness estate-wide and every consumer would silently fork a stale binary. Both directions are held here. license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0