Observed during a PR review: a first 'mix mob.deploy --native' run without --device installed the probe APK on the physical Moto AND the pool emulator, and attempted BEAM pushes to 3 iPhones (all failed app-not-installed, with a misleading 'on-device override now incomplete' warning for an app that never existed). ANDROID_SERIAL is not honored as a target filter. With agent fleets sharing a device pool this cross-contaminates other lanes' targets — an unleased probe app took the foreground on another agent's leased emulator slot this way. Asks: (1) honor ANDROID_SERIAL, or (2) require an explicit --device/--all choice when more than one device is reachable (interactive prompt or hard error in non-tty), and (3) fix the misleading override warning when the app was never installed. Companion hazard already documented for mob.push in mob's agentic-coding guide — that section should mention bare mob.deploy too.
Observed during a PR review: a first 'mix mob.deploy --native' run without --device installed the probe APK on the physical Moto AND the pool emulator, and attempted BEAM pushes to 3 iPhones (all failed app-not-installed, with a misleading 'on-device override now incomplete' warning for an app that never existed). ANDROID_SERIAL is not honored as a target filter. With agent fleets sharing a device pool this cross-contaminates other lanes' targets — an unleased probe app took the foreground on another agent's leased emulator slot this way. Asks: (1) honor ANDROID_SERIAL, or (2) require an explicit --device/--all choice when more than one device is reachable (interactive prompt or hard error in non-tty), and (3) fix the misleading override warning when the app was never installed. Companion hazard already documented for mob.push in mob's agentic-coding guide — that section should mention bare mob.deploy too.