iris bench: shared mark textures, textures that survive a new device, and a devlog that shows panics (ai-app-2 341b7a5)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -11,6 +11,31 @@ no enrolment and no permissions.
 
 The rest of this file is the runbook that was delivered with the APKs.
 
+**2026-09-08 (evening): the crash on scrolling up, and a devlog that can
+show a panic.** `iris-bench-arm64.apk` rebuilt from ai-app-2 `341b7a5`.
+
+- **The crash.** The bench built a texture per disclosure triangle -- one
+  per folded tool card, hundreds of copies of three pictures -- and the
+  path that rebuilds the renderer for a new GPU device forgot which slot
+  each was in, so a frame could ask for a texture that no longer existed
+  and the app aborted. It is one texture per shape now (three for the
+  whole screen), and a new device re-uploads what it had instead of
+  forgetting it, so the handles stay valid. On the emulator this was
+  reproducible on the *first frame*; there it now opens clean and takes
+  33 full-screen scrolls back through the fixture without complaint.
+  **Whether it was your crash is not confirmed** -- nothing recorded what
+  yours was, which is the other half of this build.
+- **The Runtime tab will show a panic now.** It only ever had one line
+  because, after a crash, Dev Updater's query starts the app for the
+  *provider alone* -- no screen, so the code that replays the previous
+  run's crash file never ran. The provider does that itself now, and the
+  crash file carries the last 80 log lines from the run that died as well
+  as the panic, replayed in order: what the app was doing, then what
+  killed it, then this run. So if it still crashes, open Dev Updater's
+  Runtime tab afterwards and send what is there.
+- Side effect worth knowing: switching away from the app and back no
+  longer re-rasterises every glyph on screen.
+
 **2026-09-08: catching a moving list, and rounded code fences that clip
 on the curve.** `iris-bench-arm64.apk` rebuilt from ai-app-2 `38bf630`.
 Two things from your last report, and both want checking on the phone