docs(testing): record live original comparison

Document the Wine-backed original start and charged-launch captures, the matching deterministic Rust states, and the remaining boundary that a chosen claw terminal was not forced in the live original.

Test Plan:
- Launch original/TDKPIN.EXE with Wine 11.15 staging
- Send keypad plus, hold Down for 1.1 seconds, release, and inspect captures
- Compare original started state with Rust launcher step zero
- git diff --cached --check

original/MECHANICS_PROGRESS.md

@@ -55,9 +55,23 @@ renamed.
   claw cadence independently of render rate.
 - Transcribe the full fixed-point flipper impulse calculation, then compare it
   with the Rust floating-point collision response.
-- Validate the reconstructed sequences against deterministic Rust traces and
-  captured frames from the original executable.
+- Force a chosen claw terminal in the live original and compare its complete
+  frame/trajectory sequence with the deterministic Rust trace.
 
 Those items are intentionally not counted as semantic parity. The readable
 C file preserves their raw constants and labels the unresolved conversion so a
 later implementation cannot silently turn an estimate into claimed evidence.
+
+## Runtime comparison on 2026-08-22
+
+Wine 11.15 (staging) ran the preserved 16-bit NE executable from this tree.
+Keypad `+` was sent to the real window and produced the one-player started
+state. Down was then held for 1.1 seconds and released; captures confirmed that
+the original plunger advances while held and launches only on release.
+
+The Rust validation mode captured the corresponding started and half-charge
+states plus closing and release frames for claw terminal 6. The original claw
+was not forced into a chosen terminal during the live session, so its claw
+parity evidence remains the decoded `1000:c79c`/`1000:eab1` control flow,
+millipixel/Real48 constants, sprite sheet, and deterministic Rust traces rather
+than a claimed live trajectory comparison.

tdkpin-rs/RECONSTRUCTION.md

@@ -57,6 +57,11 @@ decoded, build-ready subset; it does not replace that evidence archive.
 - Runtime coverage: the Linux executable was launched through the real window
   backend, the attract screen was inspected, a game was started, a ball was
   launched, collision scoring was observed, and a rendered frame was captured.
+- Original-runtime comparison: Wine 11.15 staging ran the preserved Win16 NE
+  executable; keypad `+`, a 1.1-second Down hold, release, and the resulting
+  launch were captured and compared with deterministic Rust states. A chosen
+  original claw terminal was not forced live, so claw evidence is static code,
+  decoded numeric constants, original assets, and Rust state/frame traces.
 - Deterministic mechanics coverage: named launcher, flipper, and all four claw
   terminal scenarios advance at exact 120 Hz steps, record JSON state/event
   traces, and can export the logical 640x460 render target at any requested