Fix scenario step key: use 'wait' instead of 'sleep'

- Change 'sleep' to 'wait' in boot-check.yaml
- Change 'sleep' to 'wait' in boot-full.yaml
- Wokwi CLI expects 'wait' as the valid scenario step key
- Fixes "Invalid scenario step key: sleep" error

Co-authored-by: softhack007 <[email protected]>

Author: Copilot

test/wokwi/scenarios/boot-check.yaml

@@ -10,12 +10,12 @@ timeout: 15000  # 15 seconds - increased to allow for slower CI environments
 # Simple validation: just wait and ensure the simulator doesn't crash
 steps:
   - name: "Wait for initial boot"
-    sleep: 6000  # 6 seconds
+    wait: 6000  # 6 seconds
 
   - name: "Verify simulator is still running"
-    sleep: 6000  # 6 seconds
+    wait: 6000  # 6 seconds
 
   - name: "Final stability check"
-    sleep: 3000  # 3 seconds
+    wait: 3000  # 3 seconds
 
 # If we get here without the simulator crashing, boot is successful

test/wokwi/scenarios/boot-full.yaml

@@ -10,15 +10,15 @@ timeout: 30000  # 30 seconds
 # Extended validation with more time for full system initialization
 steps:
   - name: "Initial boot phase"
-    sleep: 8000  # 8 seconds - ESP32 basic initialization
+    wait: 8000  # 8 seconds - ESP32 basic initialization
 
   - name: "WiFi AP initialization"
-    sleep: 10000  # 10 seconds - WiFi access point setup
+    wait: 10000  # 10 seconds - WiFi access point setup
 
   - name: "HTTP server startup"
-    sleep: 8000  # 8 seconds - Web server initialization
+    wait: 8000  # 8 seconds - Web server initialization
 
   - name: "Final stability verification"
-    sleep: 4000  # 4 seconds - Ensure everything is stable
+    wait: 4000  # 4 seconds - Ensure everything is stable
 
 # If we get here, WLED has fully initialized with WiFi AP and HTTP server