| 1 | # Transcript cutover acceptance |
| 2 | |
| 3 | > Historical evidence for the retired renderer. Current architecture and acceptance are documented in [Natural-flow chat](TRANSCRIPT_ARCHITECTURE.md) and [chat refactor acceptance](CHAT_REFACTOR_ACCEPTANCE.md). |
| 4 | |
| 5 | [简体中文](TRANSCRIPT_ACCEPTANCE_9777.zh-CN.md) |
| 6 | |
| 7 | The renderer slice of #9777 replaces the legacy engine atomically. It includes |
| 8 | mounted-block ResizeObserver ownership, generation-fenced cold measurements, |
| 9 | retirement of consumed native wheel travel, and one before-paint commit for |
| 10 | prefix geometry and anchor correction. Old queued geometry cannot overwrite |
| 11 | that commit. Native gestures keep authority; no second scroll writer is added. |
| 12 | |
| 13 | Acceptance covers selection, question navigation, history prepend, async |
| 14 | content growth, process/reasoning disclosure, A-to-B-to-A replacement, |
| 15 | streaming tail reachability and manual-reading ownership. Windowed rendering |
| 16 | retains the mounted-block cap. Sustained native wheel input and its release |
| 17 | are checked for reverse displacement, painted overlap and final tail distance. |
| 18 | Existing correctness thresholds must not be relaxed to qualify the cutover. |
| 19 | |
| 20 | The local production replay exercises Chromium and Playwright WebKit; the |
| 21 | platform workflow additionally exercises actual macOS WKWebView, Windows |
| 22 | WebView2 and Linux WebKitGTK. Browser emulation cannot replace these native |
| 23 | checks. Each child PR must pass its own current-head checks and integrate |
| 24 | its settings and pure-model parents before merge. |
| 25 | |
| 26 | App source-bound commands and memory qualification are separate slices. |
| 27 | Renderer acceptance does not certify whole-App heap retention or the entire |
| 28 | original integration PR. Live child PR checks are authoritative for delivery |
| 29 | status; this document records the contract rather than a permanent green |
| 30 | CI claim. |
| 31 | |
| 32 | Native finish is geometry-driven: after the sustained input phase, hosts send |
| 33 | batches of eight native events until two observations confirm the physical tail. |
| 34 | There is no fixed finishing-event count that assumes estimated height stayed |
| 35 | constant. The original GTK 45-second total watchdog, WKWebView 225-second |
| 36 | interaction watchdog, WebView2 60-second interaction budget, 4px displacement |
| 37 | and tail limits, zero blank frames, and bounded mounts remain unchanged. |
| 38 |