ViddikKeepConnectedCapturesTask
Keeps what a connectedAndroidDeviceTest run pulled, level by level.
The levels below what Gradle Managed Devices can capture are run one emulator at a time, and each run empties AGP's output directory first, so after 24, 26 and 27 only 27 was left for the report to read. This copies each run out to a directory nothing clears, for the report to read instead.
It is also what notices a run that captured everything and pulled nothing. Measured: connected runs on API 26 and 27 took all 658 captures and brought back none, with the same outcome as any other run of that suite. AGP uninstalls the test APK at the end of the run, and the captures go with it, so there is nothing left to pull from here; the run has to be repeated, and the build says so rather than leaving it to a line in the console. The level keeps what an earlier run left, and a PULLED_NOTHING_MARKER beside it has the page say so.
And a run that never got to the device: a build that failed on compilation left the level's earlier captures where they were, with nothing to tell them from this run's. ViddikPrepareConnectedEmulatorsTask runs before anything else of the module and notes which levels the run is for (PENDING_DIR); this task finalizes it as well as the test, so it runs when the test does not, and marks those levels.