Lid open during the arm wait: harness cases, laser.arm-wait-lid, operator doc

laser_lifecycle_test drives the controller's button wait through the
file-backed switch source (GF_SWITCH_FILE): a press with the lid closed
arms and nothing arms before it; the lid or the interlock loop opening
during the wait cancels the job (reason reported, alarm 3, never armed).

Acceptance catalog: laser.arm-wait-lid (operator kind - no press is
given, so nothing can fire) starts a laser job, has the operator open
the lid at the white-button prompt, and checks the cancel message,
alarm 3, armed=false, the kernel latch locked, no emission, and Idle
after $X. covers names glowforge_laser.c, glowforge_switches.c and
glowforge_switch_map.h explicitly.

LIGHTBURN.md: opening the lid or the interlock loop while the button is
lit cancels the job; a press with the lid open never arms.

docs/LIGHTBURN.md

@@ -32,7 +32,10 @@ The laser fires only inside an operator-armed window:
   requires). LightBurn simply waits; press the button and the job
   runs. If nobody presses within `laser_button_timeout_s` (default
   300 s) the job aborts with alarm 3. Stop in LightBurn (soft reset)
-  cancels the wait at any time.
+  cancels the wait at any time. Opening the lid (or a Pro's interlock
+  loop) while the button is lit cancels the job the same way — the
+  message names the reason, the latch relocks, and a press with the lid
+  open never arms; close the lid, clear the alarm, and start again.
 - One press covers one job — power changes and M5/M3 toggles do not
   re-prompt. The window relocks when the job ends (program end
   `M2`/`M30`), when the sender connection changes, or after