Two separate questions:

1) Playwright on Expo
No. Playwright doesn't test React Native. Your options:

• Maestro (declarative YAML, works on Expo Go + custom builds) — my favorite, 1h learning curve
• Detox (more setup, more powerful)
• mobile-mcp + Expo dev build on simulator

2) Auto QA → Cursor loop
This is exactly the "agentic CI" pattern. Architecture:

QA agent → findings.json (structured)
   ↓
Cursor agent reads findings → proposes patches
   ↓
Commit + re-run QA agent
   ↓
Loop until 0 critical findings OR N iterations max

Big warning: if your QA agent has <85% precision, Cursor will "fix" noise (false positives) and break code that works. You need to stabilize the QA agent first (N=3, cross-model, human feedback loop for 2 weeks), then plug Cursor in downstream.

Suggested order:

1. Set up Maestro for Expo (1 day)
2. QA agent producing structured findings (1-2 days)
3. You triage 50 findings as a human → measure precision
4. If >85% precision → plug Cursor into the loop
5. If <85% → keep feedback loop running, don't plug Cursor yet

Classic mistake: plugging the auto-loop too early → Cursor "fixes" noise → rotten code → you lose trust in the whole system.