All captures: real web app, Chromium on Linux, 1280x800 CSS pixels, dark theme, local Vite development server; no application code changes. Fresh isolated databases created with T3CODE_DEV_SEED=0. No production data used. Before: base 43915a4064b341cd040f24c1b906d87222e403de, web port 7683. Destination environment: 48e2510f-2b41-49e9-bc66-2a113283b806. Source environment: 4d0f59dd-00f9-453e-8b32-be6fe064692c. After: head 7ce31b680be95d2c23ea4d9821f53be1f94d36a5, web port 5787. Destination environment: 4d0f59dd-00f9-453e-8b32-be6fe064692c. Source environment: 48e2510f-2b41-49e9-bc66-2a113283b806. Both clients paired with both environments through the app's connectPairing command, using their web-dev origins. The real peer_environment_links table contains zero rows in each database. Each environment contains the same synthetic Release planning thread (22222222-2222-4222-8222-222222222222), created through startTurn by seed-source.js. Source text: Release decision: ship on Friday. Keep the rollout small. Both recordings execute record-interactions.js unchanged, with only the source environment parameter differing. Each starts in a fresh free replay multi-turn conversation. In order: legacy text-only paste and send; rich cross-environment paste and send; rich same-environment paste and send. Rich clipboard content is generated by the driver in the app's clipboard format, rather than copied through an OS clipboard gesture. All paste handlers, transcript transfer, send, server projection, and provider delivery run normally. The free replay provider produces canned responses; those responses are not evidence that a reasoning model understood the reference. provider-tap.mjs observes the actual stdin session/prompt frames received by that provider, without changing them. Uploaded provider-input files include only the relevant user prompt/context blocks, with attachment storage paths redacted. The synthetic transcript attachment was opened and checked for the original release decision, canonical thread ID, and source environment ID. Final stills: after the same three sends, dismissed the unrelated star-request toast and blurred the editor; each retained image matched a preceding screenshot taken at least 500 ms earlier byte for byte. Recordings and stills were visually inspected before upload. AI-assisted; verified with the tests and tools listed above.