nx_bite_sweep.nx

nx_bite_sweep.nx -- run the non-vacuity proof across every declared gate of a domain (closes seq1366). nx_gate_bite answers "can THIS gate fail?" for one gate. This is the orchestration around it: walk a domain's .gates, take each row's declared SUBJECT (field 3), and require every gate to kill a mutant. Single responsibility kept separate on purpose (rule 9) -- measuring one gate and driving a fleet are different jobs, and folding them into one organ is how a measurement tool grows a scheduler. ★NO SILENT CAPS. A row with no declared subject is reported as NO-SUBJECT and counted against the domain, never skipped quietly. That distinction is the whole point: a gate we did not test and a gate that cannot fail must not look the same in the output, or the sweep becomes the very thing it audits. ★WHY THE SUBJECT IS DECLARED, NOT DERIVED: the obvious convention (nx_X_gate.elf -> runtime/nx_X.nx) is wrong often enough to matter -- nx_raci_gate's subject is runtime/_hdl_build/nx_raci.nx. A guessed path that fails to open produces "no mutant killed", which reads identically to a vacuous gate. Guessing here would manufacture false accusations against working gates. usage: nx_bite_sweep <domain> [max_sites] (CWD = nxc2 root) exit 0 = every declared gate BITES · 1 = at least one vacuous or untestable · 2 = usage/no gates license_tier: ORIGINAL