iphone-use-qa — exploratory testing on a real iPhone

Find what is broken or confusing in one app by using it on the phone, the way a tester would. Findings come from what the phone does, never from reading the app's source. Drive the phone the way the iphone-use skill says (probe, batches, wait_for, verify); this skill only adds the QA loop and its rules.

Before you start

phone_status must say drivable:true. If the daemon released the phone after idling (released:true, recovery_owner:"daemon", no blocker), call phone_reconnect once and check phone_status again. Otherwise (a human handoff, or a blocker named in setup_blocked_on), or if it is still not drivable, report its hint and stop.
Agree on the target with the user: the app (phone_apps finds the bundle id), the areas or the build to focus on, and how long to spend. If the app needs a login, use phone_login or ask the user to sign in; never ask for the password.
Make a folder for the run, e.g. qa-<app>-<date>/, and keep everything there.