the phone assistant app, the one that talks to the agent and drives the screen, was building locally and eating the machine every time. moved the build to a hosted runner so the box stays free. tests and the build pass there, and the artifact is published on a release page, because the artifact storage quota ran out and a release is just as easy to fetch.
the build is the boring part. the interesting part is what the failures taught about controlling the phone. intents that should make anything play open the app and play nothing. sending a media command returns a happy success and changes nothing. the way that finally worked is a chain: a deep link puts the app in a known state, one accessibility tap finishes the last mile, and a proof step reads the result back from a system source of truth instead of trusting the app's word.
the same rule applies to everything else on the phone. volume changes verify by reading the volume back. a shuffle action verifies by checking the label changed. even the panel hides itself while the agent drives, because a visible overlay becomes the active window and breaks the reading.
two rules came out of it. never report success without reading state back, and never drive the phone from a window the user can see. the next feature goes through the same loop: deep link, tap, prove.