nx_dev_api.nx

nx_dev_api.nx -- SOVEREIGN DEV/CI API: development itself becomes Nishi API calls (operator 2026-07-02: "get this all setup as api calls in the nishi ecosystem ... so we dont use shitty wsl and shitty shell"). The ONE operation no existing API exposed = BUILD (compile a .nx -> ELF). This closes it, so the WSL door is retired: a client POSTs a build request over our own HTTP and reads the gate verdict back. GET /api/dev -> index (routes) POST /api/dev/build body organ=<name> -> fork/exec ./_offc/nx_sov_build_run.elf <name>, capture stdout+stderr, return {organ,exit,output} POST /api/dev/gate body organ=<name> -> build a *_gate + return GREEN/RED verdict + output GET /api/dev/status -> the job-runner receipts tail (what ran, exit codes) PURE ROUTER da_handle(req,req_n,out)->out_n (bytes in, bytes out) so the gate drives it in-process, exactly like ta_handle/ma_handle. THE DEFENSIVE BOUNDARY (rule 12): the organ name is charset-validated [a-z0-9_] only -> no path traversal, no args, FIXED-ARGV exec = injection structurally impossible. AUTH: /api/dev EXECUTES code -> the mutating routes require an X-Nishi-Cap capability token granting the tool "dev_build" (nx_cap_token: HMAC, unforgeable, least-authority, no ambient identity = confused-deputy impossible). No cap / forged / expired / wrong-tool -> 401. Secret from a keyfile (prod), const fallback (gates/dev stay deterministic) -- the tools-API convention. license_tier: ORIGINAL