nx_https_get_complete.nx

nx_https_get_complete.nx -- step 4 of the nx_https_client wiring arc. THE LAST piece before nx_https_get(url, store) works end-to-end. Takes a connected TLS 1.3 session (state == CONNECTED, app traffic keys derived in step 3c.5) + a path + a host + an out buffer. Encrypts an HTTP/1.1 GET request as an application_data TLS record under client_app_traffic_key + sends + reads the server's encrypted response records in a loop + decrypts each under server_app_traffic_key + accumulates plaintext into out_buf until peer-close (close_notify alert OR TCP EOF). Returns total bytes accumulated into out_buf on success (POSITIVE). Negative -NX_HTTPS_GC_* verdict on failure. Composes 4 shipped substrate primitives: nx_http_client_build_request -- 4-line HTTP/1.1 GET nx_tls13_record_encrypt -- AEAD wrap nx_tls13_read_record_from_fd -- partial-read framer nx_tls13_record_decrypt -- AEAD unwrap HTTP/1.1 Connection: close semantics: The shipped nx_http_client_build_request emits "Connection: close" so the server closes after responding. We read until EOF (or close_notify) and return whatever was accumulated. Per-response chunking + Content-Length parsing is a later refinement (the calling Browser arc parses HTTP body from the returned bytes). Public API: nx_https_get_complete( session, fd, path, path_len, host, host_len, out_buf, out_cap ) -> POSITIVE bytes_received | NEGATIVE -NX_HTTPS_GC_* code nx_https_gc_verdict_is_valid(v) -> 0|1 Sealed verdict: NX_HTTPS_GC_OK positive rc = bytes received NX_HTTPS_GC_BAD_STATE session not at CONNECTED NX_HTTPS_GC_BUILD_FAIL request builder returned non-positive