nx_aimode_lib.nx

nx_aimode_lib.nx -- BR50: read a Google AI Mode share link as its ANSWER TEXT, never as a script shell. WHAT THE WIRE SHOWS (measured 2026-09-18/19 with the CDP oracle ac_cdp/aimode_oracle over the operator's share https://share.google/aimode/vVS1jO66c6HI3D4YN, network capture + DOM poll): * share.google/aimode/<id> --302--> www.google.com/share.google?q=aimode/<id> --301--> www.google.com/search?...&udm=50... (a 92,807 B script shell, title "Google Search", noscript enable-JS redirect, five scripts, NO answer text). A COLD fetch of that /search url (no cookies) returns the same shell -- proven twice sovereignly (nx_research_fetch). * The FIRST /search response SETS cookies. A SECOND, cookie-WARMED GET of the same /search url (the oracle's idx=1, cookie_header_len 0->1812) returns a 406,554 B server-rendered document that is NOT the shell: it carries the AI Mode streaming containers AND, server-rendered as plain text in its markup, the continuation URL /async/folwr?... (garc/mlro/elrc/_xsrf tokens all present -- 12 hits; the cold shell has ZERO). NO JavaScript computed those tokens: they are in the SSR HTML. * A GET of that /async/folwr url (with the same cookie jar) returns a 1,452,920 B HTML fragment that carries the WHOLE conversation's answer prose ("Neo-Hookean", "Hyperelastic", "Tyranny", "Neuromorphic", "Tesla" all present). This is the ANSWER, delivered in ONE synchronous response -- no streaming wait is needed on the sovereign side (the referee browser waits; we do not). * The oracle was NOT signed in ("Sign in" in the nav) and no request that carries the answer is a POST or a batchexecute with a JS-signed body: every answer-bearing request is a plain same-origin GET. SO THE SOVEREIGN PATH IS THREE COOKIE-SHARING GETs, no js_eval (BR3), no signed session: PASS A follow share.google -> ... -> /search (cold), collecting Set-Cookie into a jar, capture final url PASS B warm GET the final /search url WITH the jar -> extract the /async/folwr continuation url PASS C GET /async/folwr WITH the jar -> the answer HTML fragment -> nx_html_to_text A sign-in / consent wall is a NAMED refusal; a shell that never yields a continuation or answer is REFUSED-NO-ANSWER by name; an empty body is REFUSED-EMPTY-BODY. COMPOSES INCUMBENTS, DUPLICATES NOTHING: the TLS-1.3 session, redirect Location resolution, cookie jar, gzip and chunked decoders are the estate's (nx_https_fetch_follow's ff_path/ff_resolve_location/ ff_collect_cookies/ff_gunzip, nx_https_get_complete's req driver, nx_http_response_parse/nx_http_dechunk, nx_https_redirect). This file writes only the jar-keeping loop those helpers were never wired into, and the answer parser. ms_find (balanced-substring) is nx_media_state's. license_tier: ORIGINAL No hw writes (Rule 26).