3.0 KiB
Chat pane refresh — 6 November 2026
Runtime client source 8eb3a44d combines the native chat-list picker (a0992eb2) and accepted opaque, active-on-top renderer (a4f6c547). Benchmark tooling follow-ups preserve native row-label compatibility. Source landed on main and ancestry was verified; unrelated desktop/export work remains untouched.
The picker reuses the sidebar's real rows and visibility filtering, excludes opened panes, and has search that only narrows that set. On narrow screens selection immediately puts the active chat in the top80% slot. Both retained threads keep stable content constraints and repaint boundaries; only a2px focus cue animates for120ms. No body opacity, body movement or per-frame transcript resizing remains. Drafts, native Back, closed keyboard on preview taps, desktop geometry and reduced motion are preserved.
Final integrated watchdog results: chat897, application143, shell123 passed; analysis clean. Release web/Android builds and APK signing-identity verification passed. Two combined real-browser flows each passed three assertions; all six final picker/top-pane screenshots under /private/tmp/pane-release-{material,cupertino}-final/ were inspected. Picker visibility/fold proof and renderer transition films are referenced in their focused notes. No physical Fold/device verification was performed.
Repeated source-mapped CPU + Flutter FrameTiming profiles use30 chats/120 rich messages at560x1000 with identical headless CPU-raster setup, drained warmup timings and confirmed10/10 switches per run. Three baseline/three accepted normal runs: framework work736.61→381.9ms (-48.2%), raster2472.51→1333.2ms (-46.1%), long-task1765→718ms (-59.3%), p95 total-frame62.7→56ms. Three rapid runs also verified every switch. A full-pane fade candidate was measured and rejected because p95 raster got worse. These are browser comparisons, not physical-device FPS claims; raw evidence is in chat-pane-performance.md.
Prepared Android 29900062, APK SHA256 f609f8d419860b4cb5b75b2f1adbeea0281239406483ee6cb5743e0dc3fc0e4e; web JS SHA256 2ee14338fc235bd0dd1ba63b7a523defca69d8887f610beaf766d5417d250b61. This combined release includes storage/retention as well as the chat improvements. It is not claimed live by this note: guarded deployment receipt is authoritative at ~/.local/share/pipelines/deployments/storage-20261106T215841Z/status.json.
The active-work gate was blocked by this agent's own Codex session. Alan requested a completion notice, so a single detached delivery worker will wait for all active turns/tasks/runs and queued prompts to finish after the reply. It verifies immutable staged hashes, preserves binary/database/client rollback copies, deploys the backend and clients, checks API plus authenticated loopback/public file hashes, then submits one clearly labelled automated completion report to this same chat. It never enables retention or requests cleanup. It refuses to downgrade a newer client, has a24-hour bound and records failures separately. No pipeline definitions or versions were authored.