Clarify open vs boot fallback guidance

Author: thymikee

README.md

@@ -195,7 +195,7 @@ Boot diagnostics:
 - Boot failures include normalized reason codes in `error.details.reason` (JSON mode) and verbose logs.
 - Reason codes: `IOS_BOOT_TIMEOUT`, `IOS_RUNNER_CONNECT_TIMEOUT`, `ANDROID_BOOT_TIMEOUT`, `ADB_TRANSPORT_UNAVAILABLE`, `CI_RESOURCE_STARVATION_SUSPECTED`, `BOOT_COMMAND_FAILED`, `UNKNOWN`.
 - Android boot waits fail fast for permission/tooling issues and do not always collapse into timeout errors.
-- Use `agent-device boot --platform ios|android` when starting a new session only if `open` fails because no booted target is available.
+- Use `agent-device boot --platform ios|android` when starting a new session only if `open` cannot find/connect to an available target.
 - Set `AGENT_DEVICE_RETRY_LOGS=1` to print structured retry telemetry (attempt, phase, delay, elapsed/remaining deadline, reason).
 
 ## App resolution

skills/agent-device/SKILL.md

@@ -27,7 +27,7 @@ npx -y agent-device
 
 ## Core workflow
 
-1. Open app: `open [app]` (open boots/activates the selected target when needed)
+1. Open app: `open [app]` (`open` handles target selection + boot/activation in the normal flow)
 2. Snapshot: `snapshot` to get refs from accessibility tree
 3. Interact using refs (`click @ref`, `fill @ref "text"`)
 4. Re-snapshot after navigation/UI changes
@@ -49,7 +49,7 @@ agent-device session list         # List active sessions
 ```
 
 `boot` requires either an active session or an explicit selector (`--platform`, `--device`, `--udid`, or `--serial`).
-Use `boot` when starting a new session only if `open` fails because no booted target is available.
+`boot` is a fallback, not a regular step: use it when starting a new session only if `open` cannot find/connect to an available target.
 
 ### Snapshot (page analysis)