diff --git a/TESTING.md b/TESTING.md
index d514756..cc60c84 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -230,16 +230,24 @@ Expected client output:
 prepared TAP adapter ... MAC ... configured and media disconnected before relay connect
 relay route pinned before TAP ...
 relay route verified before TAP activation ...
+lanparty-client-win connecting virtual MAC ... to relay ... room ROOM1
 lanparty-client-win connected as peer ...; LAN gateway connected yes (peer ...)
-relay event: LAN gateway connected as peer ...
-relay route verified after TAP activation ...
+lanparty-client-win opened TAP adapter ...
 TAP driver reports MAC ... and MTU ...
+TAP interface index ... LUID ...
+relay route verified after TAP activation ...
 client diagnostics: relay reachable yes gateway connected yes route pinned yes ...
+bridging TAP frames; relay route is pinned and TAP route policy is scoped ...
+relay event: LAN gateway connected as peer ...
 ```
 
 The route pin line ends with `(created)` or `(already existed)`. Either is OK.
 `already existed` usually means a matching relay host route was already present,
 for example after a previous crashed test run.
+You may also see TAP IPv4/IPv6 MTU, metric, and default-route protection lines
+between the connect and TAP-open lines. Those are expected.
+The lifecycle event may appear after the bridge starts because event logging
+begins once TAP and route protection are ready.
 
 The first diagnostics line may show `IP unknown`. After DHCP succeeds, a later
 line should show: