nx_diamond_probe.nx

nx_diamond_probe.nx -- ISOLATED IMPORT-DEDUP PROBE (2026-07-31), top of the diamond. QUESTION: does nx_cc include a module TWICE when it is reachable by TWO import paths? WHY: nx_cc_ingest fails `duplicate definition of arena_new` while its ENTIRE closure contains exactly ONE runtime import (nx_gzip_wrap -> nx_runtime.nx). If dedup is path/order sensitive, a diamond re-emits the second arrival. nx_cc_ingest has exactly that shape: it imports nx_x509_trust_store DIRECTLY and again via nx_https_fetch_follow. THE DIAMOND: probe -> leaf (direct arm) probe -> mid -> leaf (indirect arm) EXPECTED IF DEDUP IS CORRECT: builds clean, exit 0, run prints 7/8. EXPECTED IF DEDUP IS BROKEN: `duplicate definition of 'dl_value'` -- which would REPRODUCE the nx_cc_ingest class in 3 tiny files and hand the compiler lane a minimal repro. Either outcome is informative; a NEGATIVE result narrows the search rather than wasting it.