nx_mcp.nx

nx_mcp.nx -- THE SOVEREIGN MCP CLIENT. Retires nishi-ops/nxmcp.py (Python) and nxfsedit.ps1 (PowerShell) from the operating path: composing a tools/call envelope is FORMATTING, and formatting is an organ's job, not a script's (rule 29 -- NishiLang for everything, shell is break-glass only). nx_mcp <tool> <capfile> [argv...] any argv element of the form @@FILE:<path> is replaced by that FILE'S CONTENT (positional, because organs differ on where a payload goes -- nx_fs_write is `write <path> <content> [expect=]`, so a "content is always last" helper silently passes the expect flag AS the content). WHY THIS EXISTS, MEASURED 2026-08-10: the Python client returned `{}` on a 36,616 B source push and left the NAS file at 33,955 B -- a state matching NEITHER the new bytes NOR the previous ones, which then COMPILED CLEAN and produced a plausible binary. A transport that can silently corrupt the thing it is shipping is not a transport. ★★★★★★ A FOREIGN-RUNTIME DEPENDENCY IN THE SHIP PATH IS A DEFECT YOU CANNOT DEBUG WITH YOUR OWN INSTRUMENTS -- I could not determine the cause because the failure was inside somebody else's json encoder, and "undetermined" is the honest verdict a sovereign stack should never have to write about its own ship lane. COMPOSITION, NOT REIMPLEMENTATION: the TLS-1.3 wire is nx_mgmt_client (proven, sovereign, already the lane for /api/build|promote|deploy). This organ owns exactly ONE thing -- a correct RFC 8259 envelope. license_tier: ORIGINAL