diff --git a/emulator/NET-NOTES.md b/emulator/NET-NOTES.md
index dbcd793..758adc1 100644
--- a/emulator/NET-NOTES.md
+++ b/emulator/NET-NOTES.md
@@ -616,9 +616,17 @@ Timeline: game boot 98.9s -> floor+entry BRIGHT, all panel lamps dim
 120.7s -> entry lamps OFF; mission end 151.5s -> floor+entry BRIGHT
 (the egress hold, StateResponse state=2); StopMission arrives 154.9s ->
 full lamp sweep off, floor last, game exits. **Egress window = the gap
-between mission end and the console's StopMission send** (TeslaConsole
-= 3.4s; Console 4.10 waited a proper customer-exit delay) -- it is NOT
-a game-side timer and does not appear to depend on the exit code. Lamp
+between mission end and the console's StopMission send** -- it is NOT
+a game-side timer and does not appear to depend on the exit code.
+MEASURED BOTH CONSOLES: TeslaConsole = 3.4s AND Console 4.10 = 3.4s
+(with its printer spooling to a file). The remembered longer venue
+window is best explained by PERIOD PRINT TIME: Console 4.10 spools the
+score sheet at mission end, and a 9600-baud serial print of a multi-KB
+sheet = tens of seconds before the close follows -- the floor lights
+stayed on for exactly the score-print duration. (No egress-delay key
+exists in Console.ini / venue INIs -- checked.) The hold is genuinely
+console-gated: when the console doesn't close, the pod holds
+indefinitely (observed minutes). Lamp
 state byte: flash bits0-1 (solid/slow/med/fast), ch1 bits2-3
 (off/dim/bright), ch2 bits4-5. Extraction tool: scratchpad
 lamp_read.py pattern (tap lines are one byte each).