NET-NOTES: floor-lamp choreography measured -- egress window = console's call

RIO tap capture of a full TeslaConsole mission cycle: LampFloor 0x3E +
entry cluster (0x16/0x17/0x1e) bright at game-ready (customer entry),
off at mission drop, bright again at mission end (the state=2 hold),
all swept off the moment StopMission arrives, then game exit. The
egress window is purely the gap between mission end and the console's
StopMission send (measured 3.4s with TeslaConsole vs Console 4.10's
proper customer-exit delay) -- not a game timer, not the exit code.
Confirms the operator's remembered sequence byte for byte and pins the
TeslaSuite fix: a configurable delay before StopMission.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

emulator/NET-NOTES.md

@@ -590,6 +590,21 @@ puts the eye inside the mech's hull meshes -- z-fighting reads as a
 Not a render bug; trim back to the per-mech eye position (Mad Cat ~
 -1.8) restores the view.
 
+**MEASURED lamp choreography (2026-07-09 late, RIO tap, TeslaConsole
+close):** `LampFloor = 0x3E` ("floor lamp (entry/exit)", L4CTRL.HPP;
+lamps 0x16/0x17/0x1e form the entry cluster with it; 0x3D = Panic).
+Timeline: game boot 98.9s -> floor+entry BRIGHT, all panel lamps dim
+(ENTRY lighting -- pod lit while the customer climbs in); mission drop
+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
+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).
+
 ## Open questions / notes
 - Exact TCP listen port(s) — not in the source grep; get from NETNUB.EXE
   or a capture at milestone 3.