[isomorphisms]

Publish paired ICU responses through the existing private ingress into canonical appendfat Arena, preserving exact bytes and refusing invalid, stale or unsupported navigation.

Current implementation accepts either ICU's original eight-field capture or its complete ten-field capture. The content_range/transfer_decoding extension must be complete; duplicate/unknown fields, ranges and unsupported transfer decoders refuse before commit. Observed ISO-8859-1 is retained as an observation and remains unsupported for reader admission. The Shizuku worker selects ICU's existing HTTP/1.1 mode.

Validation:

• Actual unchanged ICU fetched the specified Google search URL on the host. HTTP/1.0 returned 426; HTTP/1.1 returned 200, one redirect and 93,166 bytes declared as ISO-8859-1.
• Replaying that exact captured body through the actual native private-ingress code commits it to canonical Arena and reopens identical bytes. Both the IB source owner and independent ai-ci source oracle refuse reader admission; the prior admitted source remains readable.
• Eight-/ten-field positive fixtures and partial-extension/range/decoder/duplicate/unknown/stale/digest/worker refusals passed locally. The stdout, nonzero-producer, denial and quoting controls pass with the explicit HTTP/1.1 command.
• Unchanged canonical ICK products were independently rehashed and reused from source 05a0cb7246c5a9f46abfbe92925812e7b607f454. The changed adapter was compiled with ICK. The local cached frontend's inability to rebuild the canonical library's Unicode division token is recorded rather than hidden by source rewriting.
• Current-head CI, including canonical execution and ARM32/ARM64 cross-builds: https://github.com/isomorphisms/ib/actions/runs/40161802163 . The inherited file-adapter fixtures now explicitly require HTTP/1.1; their source/Arena regression run is https://github.com/isomorphisms/ib/actions/runs/40161802319 .

Exact observed Google bytes/metadata and receiver failure are retained in isomorphisms/ib PR #163, “Define checked Google search URLs for IB → ICU acquisition”.

Evidence boundary: the capture used actual host ICU HTTPS; its subsequent ingress replay uses host pipes and an explicitly supplied UID, not Android Binder or Shizuku. Production transport labels in receipts do not upgrade that scope. App-owned Binder lifecycle, checked receiver/reader connection, native selectable results, restart behavior, APKs and physical C67 remain incomplete. The separate legacy file-capture eight-field adapter is outside this private-ingress repair.

The source/PFD v2 implementation remains on main through the earlier source promotion. This stacked draft is not a working browser and must not be merged merely because host checks pass. One-off execution without Flexible Pipes is explicitly authorized; independent acceptance remains required. Integration tracker: IB issue #164.