diff --git a/docs/impl/reports/USB-TABLET-LINK.md b/docs/impl/reports/USB-TABLET-LINK.md
index 82d814c..87b1002 100644
--- a/docs/impl/reports/USB-TABLET-LINK.md
+++ b/docs/impl/reports/USB-TABLET-LINK.md
@@ -109,6 +109,9 @@ Three PD unplug/replug cycles while pinging the tablet every 0.5 s:
   charging), then re-creates its USB network once. **The Orin's interface state does not reveal this outage**, so only an
   application-level heartbeat catches it.
 - Exact replug time isn't known; the first failed ping is used as its marker.
+- Repeat (plug-in at ~00:27:12): the tablet was silent for 7.8 s with the Orin's link up, then one gadget reconnect (00:27:25.1–27.0)
+  and a fresh `DHCPDISCOVER`; about **15 s** to stable. Replug consistently costs more than unplug (3.5 s).
+- At ignition, accessory power drops during cranking, so a start is likely to produce both edges back to back (not tested in the car yet).
 
 Consequence: in the car, expect a link outage of up to about 12 s at every ignition change. That is a requirement for the services
 (failure detection and redelivery; project-yukart ARCHITECTURE decision 24), not something to fix in the host setup.