test(e2e): harden Maestro waits across common subflows

Bandaid pass to stop chasing single-flow timing flakes:
- assert-signed-in: convert all assertVisible to extendedWaitUntil
  (20s for "Manage Profile", 5s for "Sign Out" and "Welcome")
- assert-signed-out: extendedWaitUntil 20s for "Welcome!" instead of
  bare assertVisible
- sign-out-via-button: extendedWaitUntil 20s for "Welcome!" + bump
  email-field wait 10s -> 25s (this is the consistently-slowest path)
- sign-in-email-password: extendedWaitUntil 20s for "Welcome!" + bump
  email-field wait 10s -> 25s, take a debug screenshot before the wait
  so future failures here are diagnosable

assertVisible has no retry; extendedWaitUntil retries until timeout,
which is what we want everywhere in CI where renders are slow.

Author: chriscanin

integration/mobile/flows/common/assert-signed-in.yaml

@@ -1,9 +1,15 @@
 # Subflow: assert the user is on the signed-in home screen.
+# Use extendedWaitUntil throughout so we tolerate slow CI renders after
+# sign-in. assertVisible has no retry; extendedWaitUntil retries until
+# the timeout elapses.
 appId: com.clerk.clerkexpoquickstart
 ---
-- assertVisible:
-    text: "Welcome"
-- assertVisible:
-    text: "Manage Profile"
-- assertVisible:
-    text: "Sign Out"
+- extendedWaitUntil:
+    visible: "Manage Profile"
+    timeout: 20000
+- extendedWaitUntil:
+    visible: "Sign Out"
+    timeout: 5000
+- extendedWaitUntil:
+    visible: "Welcome"
+    timeout: 5000

integration/mobile/flows/common/assert-signed-out.yaml

@@ -1,5 +1,6 @@
 # Subflow: assert the user is on the signed-out screen with the AuthView visible.
 appId: com.clerk.clerkexpoquickstart
 ---
-- assertVisible:
-    text: 'Welcome! Sign in to continue\.?'
+- extendedWaitUntil:
+    visible: 'Welcome! Sign in to continue\.?'
+    timeout: 20000

integration/mobile/flows/common/sign-in-email-password.yaml

@@ -2,15 +2,18 @@
 # Requires CLERK_TEST_EMAIL and CLERK_TEST_PASSWORD env vars.
 appId: com.clerk.clerkexpoquickstart
 ---
-- assertVisible:
-    text: 'Welcome! Sign in to continue\.?'
+- extendedWaitUntil:
+    visible: 'Welcome! Sign in to continue\.?'
+    timeout: 20000
 # On Android the AuthView sometimes renders its welcome text a beat before
 # the email field. Don't tap until the field is actually present so we
-# don't race the form's second render pass. If this times out, the failure
-# mode is a clear timeout that points at a real render-timing bug.
+# don't race the form's second render pass. Bumped from 10s to 25s
+# because the AuthView mount-after-signOut path is consistently slow on
+# CI and this was the most common cause of flakes.
+- takeScreenshot: debug-00-pre-email-wait
 - extendedWaitUntil:
     visible: "Enter your email or username"
-    timeout: 10000
+    timeout: 25000
 - takeScreenshot: debug-01-welcome
 # Tap the field, then long-press to bring up the selection menu and pick
 # "Select all" so we replace any pre-populated value (Clerk persists the

integration/mobile/flows/common/sign-out-via-button.yaml

@@ -5,12 +5,14 @@ appId: com.clerk.clerkexpoquickstart
     text: "Sign Out"
 - waitForAnimationToEnd:
     timeout: 8000
-- assertVisible:
-    text: 'Welcome! Sign in to continue\.?'
+- extendedWaitUntil:
+    visible: 'Welcome! Sign in to continue\.?'
+    timeout: 20000
 # After sign-out the AuthView sometimes renders its welcome text a beat
 # before the email field. Don't return from this subflow until the
 # field is actually present, so cycle flows don't race a half-rendered
-# AuthView. If this assertion times out the test surfaces a real bug.
+# AuthView. Bumped to 25s because the AuthView mount-after-signOut path
+# is consistently the slowest in this suite on CI.
 - extendedWaitUntil:
     visible: "Enter your email or username"
-    timeout: 10000
+    timeout: 25000