Android Debug Bridge

Step 1: Define the target and effect

1. DEFINE inspect state | run shell command | install/uninstall app | copy file | forward/reverse port | collect logs/bugreport/media | USB/wireless setup | server/mDNS/transport diagnosis | scripted device gate.
2. IDENTIFY host OS, authoritative SDK/adb path and version, target kind, exact serial/transport ID, Android/build/user/profile, boot/unlock/authorization state, package/component, local/remote paths/ports, required privilege, expected mutation, output destination/redaction, timeout, and cleanup.
3. CLASSIFY the command before execution: read-only | reversible session mutation | app/data mutation | device-wide/destructive. Ask explicit approval for destructive/device-wide effects not already requested.
4. READ the current ADB guide, installed adb --help, and references/safety-troubleshooting.md before using root/remount/reboot/sideload/testharness, package clear/uninstall, force-stop, permission changes, or device-global settings.
5. ROUTE bootloader unlock/flashing to a fastboot-specific workflow, app code changes to the relevant Android skill, and production fleet/device policy to Android Enterprise tooling.

Completion: one target, adb executable, command/effect class, expected output, timeout, and rollback/cleanup are explicit.

Step 2: Inspect host and device state

RUN:

python3 scripts/inspect-adb.py --json