nx_deadline_gate.nx

nx_deadline_gate.nx -- the referee for request-deadline propagation (nx_deadline_lib). The property that matters is not "does it parse a number". It is that the clamp can only ever SHORTEN a wait the caller already chose, because that is what makes this a COMPOSITION of the estate's existing per-lane timeout rulers instead of a second, rival one. So the load-bearing tooth is exhaustive over a grid: for every (deadline, now, want) tried, dl_wait_ms <= want AND >= 0. A primitive that could return more than `want` would silently extend somebody's timeout the first time it was adopted. It also asserts the PRODUCER and CONSUMER agree on the header name by reading the producer's SOURCE -- nx_sites_daemon_v2 carries its own NX_SD2_DEADLINE_HDR copy today, and a comment asking people to keep two literals in step is not a control. This tooth turns that into a RED. license_tier: ORIGINAL Read-only. No hw writes (Rule 26). expect_exit: 0