nx_build_gate.nx

nx_build_gate.nx -- the team's BUILD-CAPABILITY GATE: honestly know what it CAN and CANNOT build with the toolchain it has, and route the gap (operator: "have the nishi team build it, and if they cant, build the nishi team's capabilities to build it" -- step 0 of that is the team KNOWING it can't, and why). Diagnosed real gap: the file-based TLS daemon needs the server-side TLS-1.3 crypto, which uses the G2 wide-multiply intrinsic __umulhi64; the deployed nx_cc_known_good.elf is PRE-G2 and rejects it ('unhandled __ intrinsic: __umulhi64'). So the daemon is NOT directly buildable. Compiler feature levels: BASE (pre-G2, no __umulhi64) < G2 (knows __umulhi64, needed for x25519 field math). A target needing G2 is BUILDABLE only on a G2 compiler; otherwise NEEDS_BOOTSTRAP (if a G2 compiler's source is in the repo AND that source does not itself require G2 -- no chicken-and-egg) or BLOCKED. And bootstrapping+trusting a fresh compiler carries the team's hard-won MISCOMPILE risk, so a pinned/known-good build env is preferred. license_tier: ORIGINAL Pairs with nx_auditor + the Engineer.