docs/port/HANDOFF.md

@@ -521,9 +521,23 @@ fired. Do not use `title_static` for a duration.
 stands. ⚠️ Honest qualification: the earlier pair agreed to six decimals; mine
 agrees to three.
 
-⚠️ **Reach: one run.** The plate delay and the load stall are cross-checked
-against independent prior evidence. **The menu build-in and Ⓑ→title rest on this
-run alone.** 🟢 Re-take offered and **declined** — you author neither, you are
+⚠️ **Reach: one run — and 🔴 one of my two arguments for trusting it is
+withdrawn.** I said the plate *pulse period* proved the run was not slowed. That
+estimate rests on **one interval** at a 125 ms sample interval (±6.7 %), and
+re-running the trough-picking gives 2.628 s rather than the 2.369 I quoted —
+**+17.3 % against the corpus's 2.24 s**, not agreement. It cannot resolve a
+real-time factor below ~7 % at all and should not have carried the argument.
+✅ The conclusion survives on the other leg: the content-measured **2.247 s**
+agrees with three independent prior readings (2.13 / 2.132 / 2.138), and both its
+landmarks are sharp content transitions. A 17 % slowdown would have put it at
+2.49 s.
+
+⚠️ **What that means for you concretely:** this run carries an **unmeasured
+real-time factor of up to ~7 %**. The plate delay is anchored by agreement with
+prior runs. **The menu build-in (0.531 s) and Ⓑ→title (0.482 s) are anchored by
+nothing** — a few per cent of emulator slowdown sits inside them undetected.
+That is now the *second* reason they are provisional. **The plate delay and the
+load stall are cross-checked against independent prior evidence.** 🟢 Re-take offered and **declined** — you author neither, you are
 within ~0.1 s of both from the disc's own keyframes, and a one-run measurement
 over a decoded value gains nothing. Left provisional deliberately.