docs: the old reorder signature is history, not the delayed case's reading

docs/claude/verification.md

@@ -301,9 +301,11 @@ including the clean one, then read a reconnect instead of what it was testing:
   so `packets` falls with `frames` and `gaps` is the count of them. No warning: a one-packet hole is
   a one-packet jump in the stamps, far inside the glitch guard.
 - `--reorder-every 10`: `frames=1028 packets=1029 gaps=0`. The inverted packet lands inside the
-  20 ms reorder window and is resequenced: every datagram arrives and `gaps` is 0. The pre-resequencing
+  20 ms reorder window and is resequenced: every datagram arrives and `gaps` is 0. The
-  signature was `frames=925 packets=1028 gaps=102`; that is now the reading for
+  pre-resequencing signature was `frames=925 packets=1028 gaps=102` — an inversion cost a counter
-  `--reorder-every 10 --reorder-delay-ms 50`, which forces a late arrival past the window.
+  gap and a discarded packet, which is exactly what resequencing removes. Adding
+  `--reorder-delay-ms 50` pushes the arrival *past* the window and is the case the
+  `UDPSCOPE_PROBE_RESEQ_MS` readings above cover; it is not this row.
 - `--drop-every 1000 --drop-burst 200` at `--rate 100000 --batch 100` (1000 packets a second):
   `frames=7000 packets=7001 gaps=1600`, eight bursts of 200, and still no warning.
 - `--drop-every 1000 --drop-burst 300`, same stream: `frames=6203 packets=6204 gaps=2400` **and the