nx_https_post_complete.nx

nx_https_post_complete.nx -- HTTPS POST companion to nx_https_get_complete. Sends an HTTP/1.1 POST request with a caller-supplied body (typically application/jose+json for ACME) over a CONNECTED TLS 1.3 session, then drains the encrypted response into out_buf. Composes: nx_http_client_build_request_post -- POST line + headers + body nx_tls13_record_encrypt_v2 -- AEAD wrap (one or more request records) nx_tls13_read_record_from_fd -- partial-read framer nx_tls13_record_decrypt_v2 -- AEAD unwrap per response rec Body size: UNBOUNDED by this module (2026-09-04). The old 8 KB ceiling was not a statement about bodies -- it was an under-approximation of the TLS record limit, needed while the request was written as a SINGLE record. nx_https_req_complete now fragments across records and the request buffer is derived from body_len, so neither constraint remains. The instruction this paragraph used to give -- 'caller should fragment larger payloads explicitly' -- was never followed by any caller: they inherited the ceiling as a hand-picked constant instead, which is how the sovereign content shipper spent eleven days unable to send the chunks its own server offered. Verdict mirrors NX_HTTPS_GC_* with a PC prefix; same sealed-enum shape (positive bytes on success, negative -verdict on failure). Per Cardinals 9 (single-responsibility -- ONE round trip), 22 (composition of shipped primitives), 25 (build intelligence, don't strip features -- adds POST capability without weakening GET). license_tier: INDEPENDENT_REDERIVE genealogy_id: international-research-sources/ietf/rfc_8446 + rfc_9112 + rfc_8555 lineage_id: nishi_https_post_complete_q1