diff --git a/RIOv4_2-ANALYSIS.md b/RIOv4_2-ANALYSIS.md
index 96e78ff3..c3115644 100644
--- a/RIOv4_2-ANALYSIS.md
+++ b/RIOv4_2-ANALYSIS.md
@@ -419,11 +419,19 @@ detail in [`docs/hardware/display-board-1408.md`](../docs/hardware/display-board
   `$FD`** (`$3170`). The TX ISR sends pending ACK/NAK ahead of reply
   data (`$D8A6`). Control bytes `$FE` RESTART / `$FF` IDLE.
 - **Outbound reply delivery**: replies must be ACKed by the game; the
-  retry machine (`$D90E`/`$D9BE`) retransmits up to 4 times
-  (`INC $3184` per retry), then gives up — sends `$FE` RESTART,
-  `INC $317A`, teardown at `$DA2F` (`INC $3185`). The give-up teardown
-  is where the `$2521` wedge leak lives (see above; fixed in the patched
-  images).
+  retry machine (`$D90E`/`$D9BE`) retransmits — **5 times** (bench
+  2026-07-19; the earlier code reading of "4" was wrong) — then gives
+  up: sends `$FE` RESTART, `INC $317A`, `INC $3184` (give-up counter),
+  teardown at `$DA2F` (`INC $3185` — teardowns: ANY reply cycle that
+  needed at least one retransmission ends here, including NAK-recovered
+  ones, so `$3185` is the counter behind a lone cockpit `E0000001`).
+  The give-up teardown is where the `$2521` wedge leak lives (see
+  above; fixed in the patched images). Bench-observed await behavior:
+  the ACK wait arms only after the COMPLETE reply frame is sent
+  (mid-frame ACK/NAK/RESTART is ignored); a game NAK of the completed
+  frame triggers exactly one immediate counted retransmit; once the
+  first retry timeout lapses the cycle runs blind to give-up — a late
+  ACK cannot rescue it.
 - **RX overrun: unhandled.** The RX ISR reads SCSR/SCDR but never acts
   on the overrun flag — dropped bytes just corrupt the frame and
   surface as checksum NAKs. This is why the 125000-baud bench run
@@ -443,7 +451,7 @@ detail in [`docs/hardware/display-board-1408.md`](../docs/hardware/display-board
   `$DB07-$DB3D`: silent hang, no display, no recovery.
 - **Error counters** `$3173-$317B` (ACK/NAK/retry/give-up bookkeeping)
   and the three displayed ones `$3187/$3184/$3185` — rendered as
-  `E0 <ovf> <retry> <giveup>` by `$D5F2` at every increment.
+  `E0 <ring-ovf> <give-ups> <teardowns>` by `$D5F2` at every increment.
 
 ### Hardware (RIO_1407 sheet 2)
 
@@ -482,7 +490,13 @@ Built variants (wedge fix + threshold 5):
 | `RIOv4_2_patched_e0t5.bin` | 9600, native-game compatible | `9c21ac7199fb` |
 | `RIOv4_2_patched_31250v2_e0t5.bin` | 31250 + widened ACK-wait (FastRIO) | `b43032b016d7` |
 
-**Not yet burned or bench-verified.** To verify on hardware: burn, then
-force reply give-ups (e.g. kill the host mid-poll repeatedly) — the
-display must stay `F0000000` through the 4th event and flip to
-`E00000 05` on the 5th; `RIO_TAP`/mash regression as usual.
+**Bench-verified 2026-07-19 (9600 image, burned): PASS.** Driven by
+`RioSerialMonitor --e0test` (DTR reset → clean handshake → four
+NAK-then-ACK sub-threshold teardown cycles → one unACKed give-up
+cycle): the display held `F0000000` through the handshake and all four
+sub-threshold teardowns — stock paints `E0…` at the first — and flipped
+exactly at the 5th teardown to **`E0000105`** (`$3187`=00 overflows,
+`$3184`=01 give-up, `$3185`=05 teardowns), confirmed by eye on the
+cockpit display. Mash regression still to run. The 31250v2_e0t5 image
+is the same patch on the certified FastRIO base and is expected to
+behave identically.