Deploy AiCliSupervisorManagerWui main once large url:// RPC responses stop truncating

All code is merged: https://github.com/CodexCoder21Organization/AiCliSupervisorManagerWui/pull/65 (info card and timeline), PR 66 (view toggle), and https://github.com/CodexCoder21Organization/AiCliSupervisorManagerWui/pull/71 (ARM browser-test fix). main 2af0f900 passes 216/216 first-attempt tests.

Deploy attempt at 10:49 UTC (main 2af0f900; jar uploaded and kept, unused): home, list and conversation all returned 200 with clean first frames and the new info card. Then background enrichment failed and showed a new error, so the route was rolled back to the exact original 0.0.48 configuration (restored checks 9/9).

• The error: PersistentRpcConnection$AmbiguousRpcRequestException: RPC request 'readConversationHistory' to service 'vpn.u-corp.aiclisupervisor' has an ambiguous outcome because its transport failed after the request write began. The response broke after 1,310,678 of 1,333,487 bytes.
• The WUI requests up to INSIGHTS_READ_BYTES=1,000,000 bytes of history per conversation view.

Remaining: find which layer truncates large url:// RPC responses (UrlResolver persistent connection / UrlProtocol transport, or the supervisor daemon), fix it there, then redeploy main and verify the timeline renders. Consider separately whether the WUI should page the history instead of reading 1 MB per view. Evidence: deploying session notes (L3b findings), with screenshots and the full error text.

Original effort (archived): url://handoff/handoffs/hf-2026-10-05-aiclisupervisormanagerwui-conversation-page-rework-prs-65-66-awaiting-merge-approval Requested by the owner on 2026-10-22: drive older handoffs to completion.