fix: stabilize Maestro React Navigation flows

[thymikee]

Summary

Stabilize Maestro replay behavior hit by React Navigation CI.

Details:

• poll runFlow.when.visible briefly so conditionals can catch UI that appears immediately after a mutation, while keeping notVisible immediate
• prefer duplicate visible-text matches in the foreground overlapping screen container for transparent-stack Android snapshots
• use a longer Android directional horizontal swipe distance while keeping the lower content lane
• run local adb commands in their own process group so timeouts and aborts can clean up stuck adb shell children

Validation

• pnpm exec vitest run src/compat/maestro/tests/runtime-interactions.test.ts src/compat/maestro/tests/runtime-targets.test.ts src/compat/maestro/tests/runtime-flow.test.ts src/platforms/android/tests/adb-executor.test.ts
• pnpm build
• pnpm check:quick
• React Navigation Android failing group with local patched CLI: 6 passed, 0 failed
• React Navigation iOS tab-view-coverflow.yml with local patched CLI: passed
• Maestro iOS tab-view-coverflow.yml: passed
• Maestro Android comparison did not reach the app locally because Maestro Android driver timed out during startup

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-05-30 10:20 UTC