fix(rn): make verify-ready work in both pure and dev modes

Fixed verify-emulator-ready and verify-simulator-ready to work correctly
in pure mode where launch processes stay running in foreground.

Problem: In pure mode, launch-emulator/launch-simulator processes stay
running (with tail -f /dev/null) and never complete. The verify-*-ready
processes depended on launch-*: process_completed, which blocked them
from ever starting in pure mode.

Solution: Changed verify-*-ready to depend on sync-avds/sync-simulators
instead of launch processes. This allows verify to run in parallel with
launch, working in both modes:
- Pure mode: launch stays running, verify polls until ready
- Dev mode: launch exits after --wait-ready, verify polls until ready
- Already running: launch exits early, verify succeeds immediately

Added 5-second delay in verify for Android and 3-second delay for iOS
to give launch process time to start before polling begins.

Changes:
- test-suite-android-e2e.yaml: verify depends on sync-avds
- test-suite-ios-e2e.yaml: verify depends on sync-simulators
- test-suite-all-e2e.yaml: verify steps depend on sync, not launch
- Updated device lock files from test runs

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: abueide

examples/react-native/devbox.d/android/devices/devices.lock

@@ -14,5 +14,5 @@
     }
   ],
   "checksum": "8df4d3393b61fbbb08e45cf8762f95c521316938e514527916e4fce88a849d57",
-  "generated_at": "2026-02-20T01:50:04Z"
+  "generated_at": "2026-02-20T01:53:18Z"
 }

examples/react-native/devbox.d/ios/devices/devices.lock

@@ -10,5 +10,5 @@
     }
   ],
   "checksum": "4d5276f203d7ad62860bfc067f76194df53be449d4aa8a3b2d069855ec1f3232",
-  "generated_at": "2026-02-20T01:50:05Z"
+  "generated_at": "2026-02-20T01:53:19Z"
 }

examples/react-native/tests/test-suite-all-e2e.yaml

@@ -99,6 +99,9 @@ processes:
   # Phase 4b: Verify Android emulator ready
   verify-emulator-ready:
     command: |
+      # Wait a moment for launch to start
+      sleep 5
+
       echo "Verifying emulator is ready..."
       max_wait=120
       elapsed=0
@@ -112,8 +115,8 @@ processes:
       done
       echo "✓ Emulator ready"
     depends_on:
-      launch-emulator:
-        condition: process_completed
+      sync-avds:
+        condition: process_completed_successfully
     availability:
       restart: "no"
 
@@ -154,6 +157,9 @@ processes:
   # Phase 4d: Verify iOS simulator ready
   verify-simulator-ready:
     command: |
+      # Wait a moment for launch to start
+      sleep 3
+
       echo "Verifying simulator is ready..."
       max_wait=60
       elapsed=0
@@ -167,8 +173,8 @@ processes:
       done
       echo "✓ Simulator ready"
     depends_on:
-      launch-simulator:
-        condition: process_completed
+      sync-simulators:
+        condition: process_completed_successfully
     availability:
       restart: "no"
 

examples/react-native/tests/test-suite-android-e2e.yaml

@@ -78,6 +78,9 @@ processes:
   # Phase 4b: Verify emulator ready
   verify-emulator-ready:
     command: |
+      # Wait a moment for launch to start
+      sleep 5
+
       echo "Verifying emulator is ready..."
       max_wait=120
       elapsed=0
@@ -91,8 +94,8 @@ processes:
       done
       echo "✓ Emulator ready"
     depends_on:
-      launch-emulator:
-        condition: process_completed
+      sync-avds:
+        condition: process_completed_successfully
     availability:
       restart: "no"
 

examples/react-native/tests/test-suite-ios-e2e.yaml

@@ -76,6 +76,9 @@ processes:
   # Phase 4b: Verify simulator ready
   verify-simulator-ready:
     command: |
+      # Wait a moment for launch to start
+      sleep 3
+
       echo "Verifying simulator is ready..."
       max_wait=60
       elapsed=0
@@ -89,8 +92,8 @@ processes:
       done
       echo "✓ Simulator ready"
     depends_on:
-      launch-simulator:
-        condition: process_completed
+      sync-simulators:
+        condition: process_completed_successfully
     availability:
       restart: "no"