Environment for all four recordings - Real T3 Code iOS development client on a leased iPad Pro 13-inch (M5) simulator, iOS 27.2. - Portrait, light appearance, native column layout; original capture 2064 x 2752 pixels. - Public videos scale the entire capture to 1032 x 1376 and add a 104-pixel caption above it. - Each revision runs its own Metro bundle and server from its detached worktree. - Both revisions share the unchanged native dev-client fingerprint; each checkout's mobile:install --prepare resolved that cached client. - Each isolated server started with T3CODE_DEV_SEED=0. No live database was copied. - Same synthetic project and UUID control seeded via the real launch RPC; MCP chat created through the real t3 thread start CLI using a free deterministic replay fixture. - Each server has its own generated environment ID and CLI-generated MCP thread ID; UUID control ID and all seed content are the same. - Extra scaffolding threads were archived before the final recordings. Environment display labels were set to Evidence environment. Scripted interaction, identically on both revisions 1. Start whole-device recording and tap the target thread in the sidebar. 2. Wait for the chat; capture its accessibility state. 3. Send the app to the Home Screen. 4. Relaunch with agent-device open com.t3tools.t3code.dev --relaunch. This terminates the app before launch. No thread URL is supplied. 5. Wait for the settled result, retain it on screen, capture state, and stop recording. 6. Repeat for the UUID control. The native development shell reconnects to Metro on launch; the bundle download is retained in the uncut recording. Observed - Base 1a2a4a5e9684585c31eb55c1974fb32f8b1db2b7: MCP chat becomes New thread; UUID control restores. - Head 848c491ff498c4bd14ff71be48d180cfe1e16692: MCP chat restores with the original environment and thread IDs; UUID control restores. The read-only check-state.mjs loads the repository's development behavior observer through the Hermes inspector and records route/feed identity. It does not replace launchWorkspaceURL or route parsing. Recordings are the primary evidence. AI-assisted; verified with the tests and tools listed above.