nx_d001census.nx

nx_d001census.nx -- SIZE THE D001 POPULATION INSTEAD OF DISCOVERING IT ONE REFUSED PROMOTE AT A TIME. /api/promote REFUSES a gate that rolls its own verdict (D001): nx_gate_green cannot judge it and it records no harness.jrnl frame, so flake and erosion stay invisible for it. Correct guard. But it fires at PROMOTE time, one gate at a time, so the only way to learn the size of the problem is to keep bouncing off it -- I hit it four times before asking how many there are. *A GUARD THAT ONLY SPEAKS AT THE MOMENT OF ACTION TEACHES YOU THE POPULATION ONE REFUSAL AT A TIME.* This partitions every gate in the tree into the three states that have DIFFERENT REMEDIES, which is the whole point -- "D001" as one bucket is not actionable: OK inherits_base=1 -- nothing to do MIGRATABLE inherits=0, emits_verdict=1 -- nx_gate_dry_apply CAN rewrite it, automatable NEEDS-ANCHOR inherits=0, emits_verdict=0 -- dry_apply SKIPs it ("no verdict=GREEN tail"); needs the anchor rung, a source edit in the gate-owner lane. MEASURED: all 4 I hit are here. PROBE-FAIL is its own bucket: *AN UNPARSED PROBE MUST NEVER FALL INTO A KNOWN STATE*, because the bucket it lands in becomes the number somebody plans a migration campaign against. COMPOSES nx_gate_migrate probe -- never re-derives "is this compliant", because a second implementation of that judgement would drift from the one /api/promote actually enforces, and would disagree exactly when it mattered. ⚠ the probe BUILDS each gate (`builds=1`), so this contends for per-target build leases like any other sweep: bounded by an explicit max, resumable by skip, deadline per probe. nx_d001census <max> [skip] [timeout_ms] [dir] license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0