nx_buildq.nx

nx_buildq.nx -- QUEUE A BUILD FOR THE NEXT OPENING instead of re-issuing it by hand. WHY. `/api/build` under load answers REFUSED-LOAD: "NOTHING IS QUEUED for you anywhere -- re-issue it yourself once the load clears" -- and nx_build_admit's own header says its QUEUE verdict was DESIGNED to be absorbed by nx_orchestrate's wait-for-opening queue. Nothing ever wired the two: the queue had no predicate for headroom, and nothing seeded a build row. Measured 2026-08-18: five REFUSED-LOAD re-issues by hand in one session while the toolchain rung shipped -- a human acting as the retry loop. WHAT (composition, no new mechanism): one call seeds plan-build-<target>- : 1 <TAB> nx_sov_build_run <TAB> <target> <TAB> --build-only deployq- : BQ-<target> | title | headroom:[floor:max] | queued | build-<target> | note nx_orchestrate (the */5 poller) evaluates `headroom:` by forking nx_build_admit and FIRES the plan via nx_plan_run when the box GRANTS -- so the compile lands in buildroot/_build/<target>.sov.elf on the first pass after the opening, its rc + output snippet in planrun-build-<target>-, no human in the loop. The build itself still runs through nx_sov_build_run, so admission, lease, cache, canon and every other guard the build lane already has apply unchanged. Promotion is NOT queued here (a promote is a deliberate act with a digest); read the planrun result, then promote. DL9 (deploy, 2026-09-02) bq_dedupe_target: the queue was MEASURED idempotent by id (231 rows, 231 distinct ids, nx_store_put re-puts by id), so a second `add` of one target replaces the row rather than doubling it -- and this organ now SAYS so (ALREADY-QUEUED) instead of printing a second QUEUED receipt that read like a second row. The half of the rung that was genuinely open is CLOSE: a build that succeeds by another door (a sync /api/build, a hand nx_sov_build_run) left the queued row alive, so the poller rebuilt the same source on its next opening. `close <target> [rc]` marks the row closed with the reason, in place, by id; the poller fires only `queued` rows, so a closed row can never fire. Nothing to close is a named NO-ROW, never an error: a caller in a build lane must not fail because nobody had queued it. nx_buildq add <target> [floor_mb] [max_centiload] [--store <elf>] [--queue <prefix>] [--plan <prefix>] nx_buildq close <target> [rc] [--store <elf>] [--queue <prefix>] Both writes go through nx_store_put (THE plane write verb, provenanced, revision-logged) -- forked, never re-implemented. Fails CLOSED and LOUD: a refused seed prints the verb's own answer and exits 4. The --store/--queue/--plan overrides exist for the gate (fixture planes under /tmp); production callers never pass them. license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0