diff --git a/docs/evidence/screenshot-copy-2026-10-25.md b/docs/evidence/screenshot-copy-2026-10-25.md
new file mode 100644
index 0000000..13dc061
--- /dev/null
+++ b/docs/evidence/screenshot-copy-2026-10-25.md
@@ -0,0 +1,25 @@
+# Screenshot Save on a real Frame, 25 October 2026
+
+After PR #192 merged, Frame Control's production `list_shots()` and
+`save_shots()` paths were run from lxso2 against the real Frame. The test held
+the shared `/tmp/frame-test.lock` with an owner marker and removed only its own
+lock. A separate locked check earlier in this round found SteamVR at activity
+level 3 (standby). No new screenshot was created.
+
+- The Frame listed seven existing Steam screenshots.
+- One existing screenshot was copied to a temporary folder on the PC. Its
+  local size matched the reported remote size: **294,885 bytes**. The new
+  destination had four components below the temporary root: headset, Steam
+  account, game ID and filename.
+- Saving the same screenshot a second time returned zero new copies. A fresh
+  list then marked that screenshot as saved.
+- The temporary PC folder and its private image were removed at the end. The
+  source screenshot on the Frame was only read. Battery was **100% Full**
+  before and after.
+
+This verifies one real screenshot transfer and the repeat-save behavior. It
+does **not** reproduce two different real screenshots with the same filename;
+the account/game/headset collision case is covered by the fake-source test in
+`tests/test_shot_copy.py`. Windows and macOS physical-PC saves were not tested.
+Active passthrough in the recording mirror remains unknown because the Frame
+was in standby.
diff --git a/docs/recording.md b/docs/recording.md
index 4e1ebcc..ea54db1 100644
--- a/docs/recording.md
+++ b/docs/recording.md
@@ -115,6 +115,9 @@ folders keep both originals. Existing screenshots in the old flat
 `~/Pictures/SteamFrame/<filename>` layout stay where they are. They cannot be
 matched reliably to one headset and game, so **Copy everything now** can create
 a new, correctly identified copy. It never overwrites the old file.
+One real Frame screenshot was copied through this path on 25 October 2026;
+see the [test record](evidence/screenshot-copy-2026-10-25.md). The collision
+case was tested with separate fake sources, not two real same-name screenshots.
 
 - **Only what's new.** It copies what you take after turning it on, so the
   shots and clips already on the headset don't all arrive at once. **Copy