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 request rec) nx_tls13_read_record_from_fd -- partial-read framer nx_tls13_record_decrypt_v2 -- AEAD unwrap per response rec Body size limit: NX_HTTPS_PC_BODY_BYTES (8 KB). ACME requests are typically <2 KB (JWS-wrapped JSON over a 32-byte EdDSA key) so 8 KB gives a comfortable margin. Caller should fragment larger payloads across multiple TLS records explicitly (not auto-fragment here -- callers needing >8 KB request bodies are sufficiently rare that they should opt in). 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