mobile-emulator-start — Metro + Android emulator in a sane order

Deliver a working dev loop (emulator online → tunnel → bundler ready → app intent) without burning time on duplicate Metros, stale caches, or racing the dev client ahead of /status.

Pair with mobile-emulator-test for full QA; this skill focuses on bring-up + terminal hygiene.

Critical ordering (why this skill exists)

1. Emulator attached to adb before trusting adb reverse (or reverse again when the serial appears).
2. curl http://127.0.0.1:<PORT>/status shows packager-status:running before am start / dev-client deeplink (avoids “Cannot connect to Expo CLI” / 127.0.0.1 refused).
3. Helpers that enumerate devices once at startup may skip --launch / reverse if the emulator booted late — re-run reverse + intent after adb devices shows device.

Phase A: Read existing terminals first