/**
 * `pi-gui android <verb>` — emulator lifecycle from the CLI.
 *
 *   pi-gui android doctor            what exists, what is missing, and the fix for each
 *   pi-gui android setup --yes       install SDK pieces + create the default AVD (consented)
 *   pi-gui android start             adopt-or-launch an emulator (visible by default)
 *   pi-gui android stop              stop a managed emulator by serial
 *   pi-gui android install <apk>     install an APK into the emulator (the app under test)
 *   pi-gui android avd ensure <n>    create one more AVD from the installed image (slots)
 *
 * The DRIVER never boots or installs anything — these verbs are where lifecycle lives,
 * so a dead end inside a session can honestly name a command that fixes it. `doctor` and
 * `start` take `--json` for embedding hosts (mirasim) that parse rather than read.
 */
export declare function runAndroidCommand(argv: string[]): Promise<void>;