nx_https_url_for_fetch.nx

nx_https_url_for_fetch.nx -- step 1 of the HTTPS fetch orchestrator: parse + validate an HTTPS URL. Phase 0b §I.5 piece 1 of the nx_https_client wiring arc. Takes a NUL-terminated URL string, calls the shipped nx_url_parse to get its components, validates that scheme == "https", and defaults port to 443 when unspecified. Returns a populated NxHttpsTarget that the rest of the fetch pipeline consumes. This is a deliberately tiny primitive -- the next-step orchestrator (queued: nx_https_url_connect.nx, which does URL+DNS+TCP into a connected socket) composes this on top. Per Cardinal 22 (composition over configuration): small primitives stack into a working HTTPS fetcher. Public API: struct NxHttpsTarget { url: *NxUrl, -- shipped from nx_url port: i64, -- resolved (default 443) } nx_https_url_for_fetch(url_str, out_target) -> verdict nx_https_url_verdict_is_valid(v) -> 0|1 Sealed verdict enum: NX_HTTPS_URL_OK parse + scheme + port all good NX_HTTPS_URL_BAD_PARSE nx_url_parse returned negative NX_HTTPS_URL_WRONG_SCHEME scheme != "https" NX_HTTPS_URL_BAD_PORT port out of valid range Currently rejects http:// -- this primitive is HTTPS-only. An "http or https" variant for non-secure fetches is queued separately (nx_http_url_for_fetch.nx). Per Cardinals 9 (single-responsibility -- step 1 only; DNS / TCP / TLS are separate steps), 12 (defensive at boundaries -- scheme + port range checks), 23 (preamble names the queued variants). license_tier: INDEPENDENT_REDERIVE genealogy_id: international-research-sources/ietf/rfc_3986 lineage_id: nishi_https_url_for_fetch_q10