docs(maestro): fix five more factual errors in structured-session docs

Corrects recovery-as-two-operations, tmux-only survival on restart,
replay's durable-vs-live-state gap, snapshot-vs-replay purpose, and the
three-file persistence count.

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

docs/RESTART.md

@@ -86,10 +86,14 @@ a tmux pane:
   finish it, and no tmux pane keeping it alive underneath.
 - The **transcript survives**, in the per-session event log
   (`docs/STRUCTURED-VIEW.md#persistence-recovery-and-dead-sessions`) — a
-  graceful shutdown marks the session for one resume attempt, and the next
-  daemon replays that log into a fresh adapter connection via `session/load`.
-  An ungraceful death (a crash, `kill -9`) leaves no resume marker, and the
-  session stays dead permanently.
+  graceful shutdown marks the session for one resume attempt. Recovery is
+  two separate operations, not one: the next daemon calls `session/load` so
+  the adapter restores its own ACP session, but whatever history the
+  adapter emits during that call is discarded, not replayed into anything —
+  the daemon already has that history on disk. Separately, the daemon
+  rebuilds its own projection by folding the persisted event log back
+  through it. An ungraceful death (a crash, `kill -9`) leaves no resume
+  marker, and the session stays dead permanently.
 - **Pending approvals and their nonces do not survive.** Both live only in
   the old daemon's memory; any ACP permission request still mid-flight when
   the daemon exits is answered `Cancelled` on the way down, and a resumed