mobile-emulator-test — Native build QA on Android emulator + MCP loop

Degree of freedom: MIXED. Walk judgment and findings [HIGH freedom]; bring-up, Phase 1.5 freshness, and three-layer CRUD [LOW freedom — run exactly].

End-to-end verification of any native mobile build through a real Android emulator session, with backend truth (Supabase MCP) and crash telemetry (Sentry MCP) wired into the same loop. Catches the failure modes that pure unit tests and CI bundle builds miss: white screens, prototype-stripped cache rehydration, missing migrations, sync-disabled empty states, infinite refetch loops, and silent error swallows.

How to reason

1. Discover — stack, tabs, MCP, signed-in test account
2. Freshness — source + Metro bundle + device (Phase 1.5)
3. Walk — guest AND signed-in; every tab
4. Three-layer — UI success + DB row + cold refetch; evidence per finding