#2749 feat(maestro): support killApp via close mode

Summary

Supports Maestro killApp, which kills the app process the way the system would. On ADB-backed Android it runs am kill. iOS, Limrun and WebDriver-provider backends treat it as stopApp, and the docs and support matrix say so. There is no new public CLI surface.

• The kill precondition reads the resumed activity from the ActivityManager (AMS), not window focus. A resumed target is refused with android-kill-requires-background-app. A process that survives the kill fails with android-kill-process-survived. If no activity dump answers, the kill is refused with android-process-probe-unavailable. If the dump answers but shows nothing resumed, the kill goes ahead.
• The strict pidof check applies only to the kill's final check. Ordinary close, stopApp and relaunch keep main's behaviour.
• The Android lifecycle loads the kill code lazily. upstream/116_kill_app is no longer listed as a divergence. The preconditions are recorded in DOCUMENTED_DEVIATIONS.
• Rebased onto main as one commit, co-authored by Rohit. 30 files.

Validation

Tested commit 4661ed90c5.

• pnpm check:affected --run: green (full fail-open set; 4856 unit tests).
• pnpm maestro:conformance: 62/62 pass.
• Android, Maestro, daemon-session and replay-port suites: 2701 tests pass.

Live agent-device replay --maestro on an Android 37 emulator with a fresh daemon and no other emulators or simulators running:

• launchApp → pressKey Home → killApp: passes. Logcat shows Killing 5797:com.callstack.agentdevicelab/u0a231 (adj 700): kill background right after am kill. pidof prints nothing, and there are no lowmemorykiller or signal-9 lines.
• launchApp (stopApp: false): cold start, new pid 6043 (Start proc 6043 … for next-top-activity).
• launchApp → killApp with the app in the foreground: fails at step 2 with android-kill-requires-background-app. ResumedActivity still names com.callstack.agentdevicelab/.MainActivity, and the process survives.

Unresolved: if am kill runs before the system has finished backgrounding the app (for example a picture-in-picture app), the process may survive and the kill fail. This is an inference; it did not happen in the live runs.

🤖 Generated with Claude Code