# Chat and stage-debug delivery User authorized lifting deployment/APK restrictions for these fixes. No device tests or phone installation are authorized/claimed; deployment is web + APK feed. | Item | Source | Verification | Landing | Deployment | | --- | --- | --- | --- | --- | | Send follow-ups while busy | `91854148`: Send beside separate Stop; server queues without interruption | Both hosts: repeated follow-ups, pending-ack duplicate guard, newer draft preservation, 320px/2x text; server queued-prompt regression passes | Main | Web + APK 29880066 published and download-verified | | Streamed reasoning | `fa818341` + integration `8e980564`: live inline disclosure, active reply identity survives queued follow-ups | Full integrated check + browser visible streaming/OCR and post-follow-up update pass | Merged main; ancestry verified | Web + APK 29880066 published and download-verified | | Collapsed stage input/output | `027be68a`: Summary sections start closed | Both-host regressions fail before fixes; real browser confirms hidden bodies initially | Merged main; ancestry verified | Web + APK 29880066 published and download-verified | | Exact-visit raw input/output/memory/session debugging | `28539298`: recorded turn documents in Session with safe viewer | Both-host missing/capture/repair/repeated-visit isolation tests; real browser opens all three exact recorded files | Merged main; ancestry verified | Web + APK 29880066 published and download-verified | ## Integrated acceptance - `tool/check_full.sh`: clean analysis, all 1,762 tests pass. - `flutter build web --no-pub -o build/chat_stage_debug_web`: pass. Avoid concurrent pub-get jobs in one checkout; their generated iOS plugin symlink updates race. - `node tool/chat_stage_debug_probe.mjs build/chat_stage_debug_web build/chat-stage-debug-evidence`: 17 checks/8 captures pass. Uses the normal app and loopback protocol/artifact fixtures, actual pointer/text input and OCR for canvas-painted SelectableText. Confirms live reasoning plus text, queued follow-up without interrupt, further reasoning updates, collapsed stage fields, session export action, and exact input.md/output.md/memory.md bytes with Back restoring the same visit. - OpenCode normalization regressions `TestChatStreamRealV2Shapes` and `TestChatDeltaPartIDsNeverCollide` pass (no backend changes). - All UI code remains under app/; no production chat/run mutations or device use. - App working agreement updated as requested: authorized installers/APK delivery are allowed; default testing stays on web and device leases remain required. ## Deployment evidence - `./install --web-port 8083` succeeded. Quiescence checked before managed restart; server ping/banner reports `d915f692`, existing database/artifacts and the operator's OpenCode endpoint retained. The scratch server on 8082 was untouched. - Atomic copy of the installed bundle preserves existing public 8443/8096 URLs; rollback: `app/build/web-before-chat-stage-1792804170/`. - HTTP authentication gates and byte hashes verified at managed localhost:8083 and both public HTTPS URLs. Web JS SHA256: `f2f91fa94042f971da0b7abff634c00f87e429ee391ab2fa8b10d2e10adb8dc8`. - Repeated all 17 checks against the installed Docker bundle on both Material (desktop platform emulation, phone-sized viewport) and Cupertino browser hosts: `build/chat-stage-debug-deployed-material/` and `build/chat-stage-debug-deployed-cupertino/`, 10 captures each. Actual Android device behavior remains unverified; Android-UA browser accessibility activation was unsuitable for the pointer/AX automation, so it was not claimed as evidence. - Navigation regression against the installed bundle: 12 checks/9 captures in `build/chat-stage-debug-navigation-regression/`. - Replacement `./install --apk` succeeded with the corrected Docker limits: 414 seconds for assembleRelease, 65,119,962 bytes, build `29880066` (`0.1.29880066`). APK SHA256: `9deb1a4390248cd620473b56434257ee2774308b976704609d9a880ab51a822e`. - Installed APK matches the current source/argument cache key `dd55f13306084b1fac3b`, and ZIP integrity plus ARM64 app payload checked. - Published installer feed and the existing public preview feeds atomically. Both HTTPS ports 8443/8096 and managed localhost:8083 enforce sign-in and serve the exact version.json and APK bytes (full authenticated downloads verified). - `apksigner verify --print-certs` passes for the new APK and previous public build; signer SHA256 matches, preserving update compatibility: `9bc6109afc4076573861d24b0e2c4af8115c96a94951238d7aa78915455ec494`. Builds remain debug-signed as before, not a production signing-key migration. - Existing-feed APK rollback: `app/build/updates-before-chat-stage-29880066/` and `app/build/web/updates-before-chat-stage-29880066/`. - Download: `https://alans-macbook-pro.tail6bf4dc.ts.net:8443/updates/pipelines.apk`. Device installation and behavior remain unverified; no ADB/device tests ran. ## Build recovery The prior navigation APK build failed, not merely timed out: Docker's retained `oom` event identifies container `bc23c00f17d7`, and Gradle reports its daemon disappeared. Docker has 8,321,232,896 bytes total; the Flutter template allowed an 8 GiB Gradle heap plus separate Kotlin daemons, metaspace and workers. `app/docker/build.sh` now limits only its private copied Android build tree: 3 GiB Gradle heap, 1 GiB metaspace, two workers, in-process Kotlin compiler, no parallel Gradle projects or file watcher. Host Android settings unchanged. `sh -n app/docker/build.sh` passes; the combined APK build and signing/download checks above validate the corrected build profile.