nx_uxf_config_gate.nx

nx_uxf_config_gate.nx -- the D001 MIGRATION of nx_uxf_config_test onto nx_gate_verdict (2026-09-06). WHAT IT PROVES, AND WHY IT IS THE CHEAPEST EXTENSION IN THE FAMILY: a brand-new domain joins the envelope with ONLY a codec id and ZERO envelope change. A config record gets a self-describing UXF_CONFIG CID that cannot collide with the SAME CONTENT under UXF_DATA or UXF_MEDIA, and the canonical encode makes field order irrelevant. That is law 4 (extensible, data and functionality on independent clocks) at its cheapest. This gate is ALSO the evidence behind the FM1 matrix row's claim that one envelope carries every profile: FM1 asserts DATA is nxc1-01, DOC nxc1-02, MEDIA nxc1-03 and CONFIG nxc1-04, and the profile-collision teeth here are what make that a measurement rather than a description. ALL FOUR ORIGINAL TEETH PRESERVED IN ORDER AND PREDICATE, plus the values emitted for outside adjudication. HONEST NOTE CARRIED FORWARD FROM THE ORIGINAL, NOT QUIETLY DROPPED: the richer variant that PARSES a real JSON config hit a repeatable nx_cc empty-.s compile failure, so the config PROFILE is proven here and full JSON and YAML config PARSING remains a separate toolchain rung. Nothing below claims otherwise. license_tier: ORIGINAL No hw writes (Rule 26).