nx_editor_loop_gate.nx

nx_editor_loop_gate.nx -- the no-JS edit loop end-to-end: emit a native form (0 JS), POST an op, the engine applies it, the re-render REFLECTS the change, unknown ops are rejected -- and now, the SAME posted vocabulary driving the operation log so the loop has real multi-level undo and redo with still zero JavaScript. MIGRATED OFF D001, 2026-08-25. This gate used to roll its own pass/fail counters and print its own VERDICT line, which is why /api/promote refused it: nothing outside could read its outcome. It now inherits nx_gate_verdict, so declared teeth and executed teeth are the same number by construction and the exit code carries the verdict. L1..L5 are the five assertions it already made, on the same fixtures with the same expected values -- they are the REGRESSION GUARD for the snapshot surface. L9 IS THE ANTI-VACUITY TOOTH. A single posted undo proves nothing about a log: the one-deep snapshot the canvas already had passes that. Three posted ops followed by three posted undos is the smallest test the snapshot design cannot pass, and it is driven entirely through the POSTED op strings, which is the thing a browser can actually reach. L12 GUARDS THE OTHER DIRECTION: extracting the shared button block must not have leaked the new undo and redo verbs onto the snapshot surface, which cannot honour them. Gate scratch lives under /tmp/<gate>/ so it can never share a fixture with a production beat. 100% sovereign. expect_exit: 0