nx_isa_loongarch64_gate.nx

nx_isa_loongarch64_gate.nx -- THE LOONGARCH64 CONFORMANCE RULER. WHY IT EXISTS: the estate carries ten sovereign ISA interpreters in NishiLang. On 2026-09-03 nx_isa_conform_gate measured five of them and printed, in its own output, the list of the five it could not speak for: "UNMEASURED: armv7a cortexm loongarch64 s390x sparc64 -- each owes a manual-derived KAT block here". This organ pays the loongarch64 half of that debt. LoongArch is a sovereign national ISA and therefore a first-class deploy target for a sovereign estate: "we can run LoongArch" has to be a measurement, not a claim. WHY A SEPARATE ORGAN AND NOT A BLOCK INSIDE nx_isa_conform_gate: five ISA lanes were working concurrently on 2026-09-03 and this estate loses concurrent edits to one file silently. One arch, one organ, one ratchet file, one owner -- the same "one subject per row, and the writer owns its own file" rule that split the shared gatereg log. The SHAPE is copied from the incumbent deliberately, so a reader who knows one knows all of them. THE LAW THIS ORGAN OBEYS: expectations come FROM THE LOONGARCH REFERENCE MANUAL, never from reading nx_emu_loongarch64.nx and writing down what it happens to do -- that would calibrate the ruler to the subject it exists to judge. Every opcode constant below is declared HERE, independently of the interpreter's own constant table, so a disagreement between the two is a finding rather than a shared typo. The interpreter's decoder was read only to learn which classes are IMPLEMENTED versus MISSING, which is a question about coverage and not about expected values. FIVE OUTCOMES, NEVER ONE: PASS ran and matched the manual-derived expectation WRONG-ANSWER ran to completion and computed the wrong value UNSUPPORTED hit an instruction class the interpreter does not decode RAN-OFF-END the loop ended with no exit syscall / step budget spent FAULT bad pc, or a guest address outside the arena An unimplemented class and a miscomputed result need OPPOSITE fixes, and only the first is a missing feature. Collapsing them into FAIL is what makes a gap unactionable. WHAT THIS RULER FOUND, 2026-09-03, and what was then fixed in the