Make the Rust client the sole app

app/bench-fixture/generate.py

@@ -1,13 +1,12 @@
 #!/usr/bin/env python3
-"""Generates transcript.jsonl -- the synthetic fixture P0's benchmark opens in both apps.
+"""Generates transcript.jsonl -- the synthetic fixture the benchmark opens.
 
-Deterministic (fixed seed), so a Compose bench APK and an iris bench APK draw byte-identical
-content: the point of the fixture is a like-for-like comparison, not a realistic one.
+Deterministic (fixed seed), so runs draw byte-identical content.
 
 Never a real transcript -- see AGENTS.md's ui-sandbox.sh, which this borrows its vocabulary
 style from (headings, code fences, a table, a link) rather than reusing its Claude-Code JSONL
 shape. This file's shape is the *app's own event model* instead: one JSON object per line,
-matching what GET /sessions/{id}/transcript returns and what Events.kt's parseSeqEvent reads
+matching what GET /sessions/{id}/transcript returns
 (server/src/session/driver.rs is the source of truth for the field names).
 
     ./generate.py                      writes transcript.jsonl and bench1.png/bench2.png here
@@ -54,7 +53,7 @@ DELTAS_PER_BLOCK = (4, 12)
 # stress for one-shot shaping and puts a row right on the cap boundary, where nothing else is.
 #
 # It is *not* streamed: the repeated-reshape pathology needs a growing block, and that lives in
-# `app-rust/tests/frame_profile.rs`'s `what_reshaping_a_growing_message_costs`, where it can be
+# the UI profiling rig's `what_reshaping_a_growing_message_costs`, where it can be
 # iterated on in a second rather than in a two-minute phone run. Note that the cap would not save
 # a real one anyway -- `row::build_row`'s `cap` is deliberately `false` for the live tail, because
 # a row that grew while capped would appear to stop growing, so a streamed block's shaping cost