Delete TRANSCRIPT_RENDERING.md, which was all finished work

The file was a week's record of the transcript work, and everything in its
architecture, techniques and rejected sections has landed -- so it was a log
of how the code got here, which the code's own comments and AGENTS.md
already carry. Kept only what existed nowhere else: stream-bench.sh,
trace-draw.sh and the two emulator-loop traps go to AGENTS.md beside
transcript-bench.sh, along with the standing rule to run the benches either
side of a transcript change; GrapheneOS's broken System Tracing goes to
~/.claude/MACHINE.md, since it is about the phone rather than this project.

Its one unfinished item -- the reconnect loop after a restart onto a
streaming session, which may already have been fixed by the restore's
one-event-per-request fix -- moves to TODO.md.

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

TODO.md

@@ -16,6 +16,19 @@ one in place when it turns out to need a decision.
       would show exactly as "sometimes". Confirming it means driving a real
       stream-json session and sending it messages in both states.
 
+## App — reconnect
+
+- [ ] Restarting the app onto a session with a saved anchor, while a long
+      reply was streaming, left it reconnecting every 1.5s
+      (`RECONNECT_DELAY_MS`) with the spinner up until the server was
+      restarted. `events?after=N` more than `CATCH_UP_LIMIT` (200) behind
+      answers `reset` plus the newest 200 *raw* deltas -- a window starting
+      mid-message -- and the reset clears `items`, which is the state the
+      restore loop then pages against. **May already be fixed:** the
+      restore's one-event-per-request bug was part of what made it so
+      visible and has since been fixed, so the first thing to find out is
+      whether this survives that. Found 2026-09-03.
+
 ## Session settings
 
 - [ ] Autocompact belongs in session settings; empty disables it, which is the