Verifying Android changes on a device, without tests

Verify an Android change on a device or emulator when the project has no test suite, and avoid reading a blind check as a passing one. Use when: (1) you changed Android code and want evidence it works beyond "it compiled", (2) a UI assertion driven by `uiautomator dump` reports text is missing, (3) `adb shell run-as` fails with "not debuggable", (4) a release build misbehaves while debug is fine, (5) you are about to conclude a feature is broken because a grep over a dump, a dex file, or logcat came back empty. Covers the build-install-drive-read loop, tapping by label instead of coordinates, mocking location, and the calibration discipline that keeps an unplugged cable o…