StageDroid & Test Device Management (state-droid-remote-device)

Self-contained module for discovering and controlling remote Android devices via StageDroid (https://github.com/hereisderek/StageDroid), local USB/Wireless ADB devices, and Google Android CLI Virtual Devices (AVDs). Also manages sub-agent device pool leasing, sleeping/passcode-locked screen wakeup, and multi-density / window-inset UI verification.

When to Use

• Discovering StageDroid servers via mDNS (_stagedroid._tcp), environment variables (STAGEDROID_HOST, STAGEDROID_PORT, ADB_SERVER_SOCKET), or local ports (3000 / 3443)
• Inspecting live StageDroid server capabilities via GET /skill, GET /status (/status.json), GET /api/discovery, and GET /api/devices
• Bridging remote StageDroid devices locally via Virtual adbd (adb connect <host>:<adbPort> on ports 51001+) or the Central Smart ADB Proxy (ADB_SERVER_SOCKET=tcp:<host>:50370 or adb -H <host> -P 50370)
• Managing a limited pool of physical/remote/virtual test devices and assigning leases to feature-named sub-agents or the Coordinator
• Waking a sleeping device, unlocking a PIN/passcode lockscreen, and auditing UI across screen sizes, densities, font scales, status bars, display cutouts, and bottom navigation bars

1. StageDroid Capability & Device Discovery Hierarchy

Always resolve StageDroid capability instructions in this order (automated by ./scripts/device-check.sh). Device discovery may still query a reachable server for its live inventory; this precedence is for the instructions an agent follows: