nx_moonraker_client.nx

nx_moonraker_client.nx -- request-construction layer for the Klipper Moonraker HTTP API. Composes raw byte buffers that an HTTP client (nx_http_client or nx_https_client) sends over a socket to a Klipper printer's Moonraker server. Per NISHI_3D_PRINT_BASELINE_2026_05_19 §3: Moonraker speaks HTTP (file transfer + most endpoints) + JSON-RPC over WebSocket (events). v1 of this primitive handles the HTTP slice: GET /printer/info -- printer state POST /printer/print/start -- start print from named file POST /printer/print/cancel -- abort active print POST /printer/objects/query -- subscribe to object updates File upload (POST /server/files/upload multipart) deferred to v2; for v1 the operator places the .gcode on the printer via scp/sftp then calls /printer/print/start with the filename. WebSocket event subscription deferred to v2; v1 uses HTTP polling of /printer/objects/query. Moonraker explicitly supports both (per https://moonraker.readthedocs.io/external_api/introduction). API key handling: Moonraker uses X-Api-Key header for authenticated requests. v1 accepts an api_key parameter at construction time and adds the header to every request when non-NULL. JSON safety: v1 assumes filenames contain only [a-zA-Z0-9._-/]. Quotes and backslashes in user filenames will break the JSON. v2 will compose nx_json_emit (already shipped) for proper escaping. Per cardinal feedback-engineering-sciences-bits-up-3d-print-first: this primitive is one of the FIRST examples of substrate primitives composing into a real device-control workflow (operator -> substrate -> printer over network). Same pattern will apply to nx_cnc_client (Mach3 / LinuxCNC), nx_voron_klipper (variant), nx_marlin_serial (older firmware), etc. license_tier: ORIGINAL