diff --git a/findings/control-flow/tail-rng-ledger.md b/findings/control-flow/tail-rng-ledger.md
index 02d8417..73d7984 100644
--- a/findings/control-flow/tail-rng-ledger.md
+++ b/findings/control-flow/tail-rng-ledger.md
@@ -154,6 +154,18 @@ each other.
 This is the pair a standalone should be tested against first: it is a byte-identical oracle *with a known
 RNG cost attached*, which none of the eleven corpus saves has.
 
+**A second pair was produced by the later per-site run and agrees the same way.**
+`z2-endturn.sav` → `z2-autosave.sav` (the turn-4 → turn-5 bracket of `ref-turn2`) gives `left` 395 → 375,
+`twists = 0`, **20 words** — matching both the boundary ledger's bracket for that turn and §11's per-site
+sum. So on turn 5 of `ref-turn2` **three instruments that share no code path agree on 20**: a hook reading
+process memory around a phase boundary, a set of detours keyed by return address, and the two save files on
+disk.
+
+| pair | turns | `left` | words |
+|---|---|---|---|
+| `z-t6-endturn` → `z-t6-autosave` | 5 → 6 | 375 → 357 | **18** |
+| `z2-endturn` → `z2-autosave` | 4 → 5 | 395 → 375 | **20** |
+
 ---
 
 ## 4. Lane K's inference, settled
diff --git a/verify/results/shim/tailrng/z2-autosave.sav b/verify/results/shim/tailrng/z2-autosave.sav
new file mode 100644
index 0000000..070b8e9
Binary files /dev/null and b/verify/results/shim/tailrng/z2-autosave.sav differ
diff --git a/verify/results/shim/tailrng/z2-endturn.sav b/verify/results/shim/tailrng/z2-endturn.sav
new file mode 100644
index 0000000..fbf460a
Binary files /dev/null and b/verify/results/shim/tailrng/z2-endturn.sav differ