Require the devtools wrappers for build/test and launch verification

Each of these happened here and was reported as fact: Gradle running against a
different directory after a silent `cd` failure; `adb shell monkey` reporting a
healthy app as crashed and a crashed app as healthy on the same emulator minutes
apart; and `adb install` refusing a filename into /dev/null, leaving the previous
build installed and under test.

Points at /workspace/devtools, which reports from exit codes, parsed JUnit XML,
and a logcat capture started before launch.

Documentation only — no production code touched, so no red step applies.

0 files changed, 0 insertions, 0 deletions