@appium/mcp-documentation 1.0.3 → 1.0.4

package/src/resources/submodules/appium-skills/skills/environment-setup-node/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: "environment-setup-node"
+description: "Prepare and validate Node.js and npm environment"
+metadata:
+   last_modified: "Thu, 12 Mar 2026 03:45:00 GMT"
+
+---
+# environment-setup-node
+
+## Goal
+Prepares a stable Node.js and npm environment by validating the active Node runtime, confirming npm availability, and checking basic npm connectivity and health diagnostics.
+
+## Decision Logic
+- If `node` is missing or major version is `< 20`: install/upgrade Node.js to active LTS.
+- If a maintained Node version manager exists (`nvm`, `fnm`, `asdf`): use it as the primary way to install/switch Node versions.
+- If no Node version manager is available on Windows: install `fnm` with `winget` and continue non-interactively.
+- If Windows shell cannot find `node` after `fnm` setup: configure PowerShell profile to initialize `fnm`, then open a new terminal (or reload profile).
+- If `npm` is unavailable: repair npm environment before continuing.
+- If `npm ping` fails: resolve registry/network configuration before continuing.
+
+## Instructions
+1. **Detect Node version management tools**
+   ```bash
+   command -v nvm || true
+   command -v fnm || true
+   command -v asdf || true
+   ```
+   Windows PowerShell:
+   ```powershell
+   Get-Command fnm -ErrorAction SilentlyContinue
+   Get-Command nvm -ErrorAction SilentlyContinue
+   Get-Command winget -ErrorAction SilentlyContinue
+   ```
+   Prefer this order when available: `fnm` / `nvm` / `asdf`.
+   If none is available on Windows, install `fnm` non-interactively and continue:
+   ```powershell
+   winget install Schniz.fnm --accept-source-agreements --accept-package-agreements
+   ```
+   Then initialize `fnm` in the current shell:
+   ```powershell
+   $fnmDir = "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Schniz.fnm_Microsoft.Winget.Source_8wekyb3d8bbwe"
+   if (Test-Path $fnmDir) { $env:PATH = "$fnmDir;$env:PATH" }
+   fnm env --shell powershell | Invoke-Expression
+   fnm install --lts
+   fnm use lts-latest
+   fnm default lts-latest
+   ```
+   Persist for all new Windows PowerShell sessions (beginner-friendly):
+   ```powershell
+   $profileDir = Split-Path -Parent $PROFILE
+   if (-not (Test-Path $profileDir)) { New-Item -ItemType Directory -Force $profileDir | Out-Null }
+   if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Force $PROFILE | Out-Null }
+   $fnmDir = "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Schniz.fnm_Microsoft.Winget.Source_8wekyb3d8bbwe"
+   Add-Content $PROFILE "`n# fnm bootstrap"
+   Add-Content $PROFILE ('$env:PATH = "{0};$env:PATH"' -f $fnmDir)
+   Add-Content $PROFILE 'fnm env --shell powershell | Invoke-Expression'
+   ```
+   Profile location example on Windows PowerShell:
+   ```powershell
+   $PROFILE
+   ```
+   If `npm` is blocked with a script policy error (`npm.ps1 cannot be loaded`), set per-user execution policy:
+   ```powershell
+   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser -Force
+   ```
+   Then open a new terminal tab, or reload profile in current terminal:
+   ```powershell
+   . $PROFILE
+   ```
+
+2. **Verify Node and npm availability**
+   ```bash
+   node -v
+   npm -v
+   ```
+   Windows PowerShell:
+   ```powershell
+   node -v
+   npm -v
+   ```
+
+3. **Validate npm connectivity**
+   ```bash
+   npm ping
+   ```
+   Windows PowerShell:
+   ```powershell
+   npm ping
+   ```
+   Ensure connectivity succeeds before continuing.
+
+4. **Validate active Node runtime details**
+   ```bash
+   node -p 'process.versions.node'
+   ```
+   Windows PowerShell:
+   ```powershell
+   node -p "process.versions.node"
+   ```
+   Confirm the runtime is an active LTS release; if not, switch Node version using the detected version manager.
+
+5. **Windows troubleshooting quick checks (when `node` is still not found)**
+   ```powershell
+   $PROFILE
+   Test-Path $PROFILE
+   Get-Content $PROFILE
+   Get-Command fnm -ErrorAction SilentlyContinue
+   Get-Command node -ErrorAction SilentlyContinue
+   ```
+   If `Get-Command node` is empty, run:
+   ```powershell
+   . $PROFILE
+   fnm use lts-latest
+   node -v
+   npm -v
+   ```
+
+6. **Agent completion criteria**
+   Mark complete only when all are true:
+   - `node -v` and `npm -v` succeed
+   - npm registry connectivity check succeeds (`npm ping`)
+   - active Node runtime is an LTS release
+
+## Constraints
+- Prefer Node.js LTS versions only.
+- Prefer maintained version-managed Node installations (`fnm`, `nvm`, `asdf`) when available.
+- Avoid using `sudo` in setup commands; prefer user-space tooling when permissions are restricted.
+- Use deterministic terminal checks, not assumptions.

package/src/resources/submodules/appium-skills/skills/environment-setup-uiautomator2/SKILL.md

@@ -0,0 +1,225 @@
+---
+name: "environment-setup-uiautomator2"
+description: "Set up and validate a UiAutomator2 Appium environment on Android"
+metadata:
+   last_modified: "Mon, 27 Apr 2026 22:00:00 GMT"
+
+---
+# appium-uiautomator2-environment-setup
+
+## Goal
+Prepares a reliable Appium UiAutomator2 execution environment by installing Node.js and Appium prerequisites, configuring Android and Java dependencies, running Appium doctor checks, and iterating until doctor reports `0 required fixes needed`.
+
+## Decision Logic
+- If the host OS is not macOS, Linux, or Windows: stop and ask the user to use a supported OS.
+- If current Node.js does not satisfy `engines.node` for both `appium` and `appium-uiautomator2-driver`: install/upgrade Node.js to a compatible active LTS version.
+- If Appium CLI is not installed: install `appium` globally.
+- Use global npm/Appium commands by default (`npm install -g appium`, `appium ...`).
+- Use local Appium commands (`npx appium ...`) only when the user explicitly requests local execution.
+- If `appium` resolves to an older Node-managed path than the active `node`/`npm` environment, reinstall Appium globally under the active Node runtime before continuing.
+- If Android SDK prerequisites are missing (`adb`, emulator binary, SDK packages): run `environment-setup-android` first.
+- If the user explicitly requests media features that require FFmpeg: run `environment-setup-ffmpeg` before final validation.
+- If the user explicitly requests automatic bundletool setup: run `environment-setup-bundletool` before final validation.
+- Always include host device/emulator inventory in the final skill result (connected devices, emulator version, and AVD list).
+- If the `uiautomator2` driver is not installed: install it via Appium CLI.
+- If install returns "already installed", ignore the error and continue (or run driver update).
+- If `appium driver doctor uiautomator2` reports missing dependencies: resolve each missing item and re-run doctor.
+
+## Instructions
+1. **Prepare Node.js + npm environment**
+   macOS/Linux:
+   ```bash
+   node -v
+   npm -v
+   ```
+   Windows PowerShell:
+   ```powershell
+   node -v
+   npm -v
+   ```
+   If `node` is missing, run `environment-setup-node` first (including Windows PowerShell profile bootstrap), then open a new terminal or run `. $PROFILE`, and re-run the commands.
+   Windows PowerShell session bootstrap (recommended before any `appium` command in fresh/background terminals):
+   ```powershell
+   $fnmDir = "$env:LOCALAPPDATA\Microsoft\WinGet\Packages\Schniz.fnm_Microsoft.Winget.Source_8wekyb3d8bbwe"
+   if (Test-Path $fnmDir) { $env:PATH = "$fnmDir;$env:PATH" }
+   fnm env --shell powershell | Invoke-Expression
+   fnm use lts-latest
+   ```
+
+2. **Install Appium npm command**
+   ```bash
+   npm install -g appium
+   export APPIUM_HOME="$HOME/.appium"
+   appium driver install uiautomator2 || appium driver update uiautomator2
+   appium driver list --installed --json || appium driver list --installed
+   ```
+   Before installing drivers, ensure `APPIUM_HOME` is writable by the current user. If `appium` fails with an Appium-home writeability error, fix that path or set `APPIUM_HOME` explicitly and retry.
+   Prefer `--json` output for machine-readable verification. Confirm a `uiautomator2` key is present; only fallback to plain-text output when `--json` is unsupported.
+   If the install command fails only because `uiautomator2` is already installed, continue and do not stop preparation.
+
+3. **Validate Appium npm commands and Node compatibility (after driver setup)**
+   macOS/Linux:
+   ```bash
+   export APPIUM_HOME="$HOME/.appium"
+   appium -v
+   appium driver list --installed --json || appium driver list --installed
+   npm view appium engines --json
+   npm view appium-uiautomator2-driver engines --json
+   ```
+   Windows PowerShell:
+   ```powershell
+   appium -v
+   appium driver list --installed --json; if ($LASTEXITCODE -ne 0) { appium driver list --installed }
+   npm view appium engines --json
+   npm view appium-uiautomator2-driver engines --json
+   ```
+   If current Node.js does not satisfy the reported `engines.node` ranges, install/upgrade Node.js to a compatible active LTS version and re-run the setup checks.
+
+4. **Run Android environment prerequisite skill**
+   Before UiAutomator2 doctor checks, execute `environment-setup-android` and do not continue until it passes completion criteria.
+
+5. **Verify Android prerequisites from this skill context**
+   macOS/Linux:
+   ```bash
+   export APPIUM_HOME="$HOME/.appium"
+   command -v adb
+   adb version
+   echo "$ANDROID_HOME"
+   ls "$ANDROID_HOME/emulator/emulator"
+   test -x "$ANDROID_HOME/emulator/emulator" && echo "emulator binary: OK"
+   ```
+   Windows PowerShell:
+   ```powershell
+   Get-Command adb.exe -ErrorAction SilentlyContinue
+   adb.exe version
+   $env:ANDROID_HOME
+   Test-Path "$env:ANDROID_HOME\emulator\emulator.exe"
+   if (Test-Path "$env:ANDROID_HOME\emulator\emulator.exe") { "emulator binary: OK" }
+   ```
+
+6. **Report connected devices and emulator inventory in task result**
+   macOS/Linux:
+   ```bash
+   export APPIUM_HOME="$HOME/.appium"
+   adb devices -l
+   "$ANDROID_HOME/emulator/emulator" -version
+   "$ANDROID_HOME/emulator/emulator" -list-avds
+   ```
+   Windows PowerShell:
+   ```powershell
+   adb.exe devices -l
+   & "$env:ANDROID_HOME\emulator\emulator.exe" -version
+   & "$env:ANDROID_HOME\emulator\emulator.exe" -list-avds
+   ```
+   In the result summary, explicitly state whether emulator preparation was skipped because either connected devices already existed or one/more AVDs already existed.
+
+   Optional shared dependency:
+   - If the user explicitly requests FFmpeg-related capability, run `environment-setup-ffmpeg` before continuing.
+   - If the user explicitly requests bundletool installation, run `environment-setup-bundletool` before continuing.
+
+7. **Run Appium doctor for UiAutomator2 and fix in a loop**
+   ```bash
+   export APPIUM_HOME="$HOME/.appium"
+   appium driver doctor uiautomator2
+   ```
+   Use `0 required fixes needed` as the pass/fail gate. Optional warnings are non-blocking. If required fixes remain, apply targeted fixes and re-run.
+   For deterministic automation, parse the doctor output for that exact phrase instead of relying on visual formatting.
+   `gst-launch-1.0` / `gst-inspect-1.0` warnings are optional for basic session execution, but recommended if you need screen-streaming features.
+   Bash gate example:
+   ```bash
+   DOCTOR_OUT="$(appium driver doctor uiautomator2 2>&1)"
+   echo "$DOCTOR_OUT" | grep -q "0 required fixes needed" || { echo "$DOCTOR_OUT"; exit 1; }
+   echo "$DOCTOR_OUT" | grep -E "0 required fixes needed|optional fix"
+   ```
+   PowerShell gate example:
+   ```powershell
+   $doctorOut = appium driver doctor uiautomator2 2>&1 | Out-String
+   if ($doctorOut -notmatch '0 required fixes needed') { throw "Doctor required fixes remain" }
+   $doctorOut | Select-String '0 required fixes needed|optional fix'
+   ```
+   AI-assisted fallback (only if exact phrase matching is inconclusive due output-format changes):
+   1. Re-run doctor once and capture full output (`appium driver doctor uiautomator2 2>&1 | tee /tmp/appium-doctor-uiautomator2.log`).
+   2. Ask an AI agent to classify required vs optional findings from the captured output.
+   3. Accept a pass only when the output clearly indicates zero required issues (for example: no required-fix section and no required-check failures).
+   4. If still ambiguous, mark status as `needs-manual-review` and do not mark the skill complete.
+
+8. **Start Appium server smoke test**
+   ```bash
+   export APPIUM_HOME="$HOME/.appium"
+   appium server
+   ```
+   Windows PowerShell recommended form (for deterministic log checks):
+   ```powershell
+   appium server --log "$env:TEMP\appium-uia2-smoke.log" --log-level info
+   ```
+   Keep this server process running in Terminal A.
+   In Terminal B, run:
+   ```bash
+   curl -s http://127.0.0.1:4723/status
+   ```
+   First confirm `/status` responds successfully.
+   Windows PowerShell reliable variant (recommended on Windows due to `curl` alias behavior):
+   ```powershell
+   $ok = $false
+   for ($i = 0; $i -lt 20; $i++) {
+      try {
+         $resp = Invoke-RestMethod -Uri "http://127.0.0.1:4723/status" -Method Get -TimeoutSec 5
+         if ($resp.value.ready -eq $true) {
+            $ok = $true
+            $resp | ConvertTo-Json -Depth 5
+            break
+         }
+      } catch {
+         Start-Sleep -Milliseconds 500
+      }
+   }
+   if (-not $ok) { throw "Appium /status did not become ready in time" }
+   ```
+   Then confirm startup/readiness from server logs and ensure the `Available drivers:` block contains `uiautomator2` (for example: `- uiautomator2@7.0.0 (automationName 'UiAutomator2')`).
+   If startup banner logs are not available in your terminal integration, use this fallback verification path:
+   - `appium driver list --installed --json` includes `uiautomator2`
+   - `/status` reports server readiness
+   Windows PowerShell log verification example:
+   ```powershell
+   Get-Content "$env:TEMP\appium-uia2-smoke.log" | Select-String "listener started|Available drivers:|uiautomator2@"
+   ```
+   After smoke validation, clean up the running Appium server:
+   - In Terminal A, stop the server with `Ctrl+C`.
+   - Verify no leftover Appium server process (Terminal B, macOS/Linux):
+   ```bash
+   pgrep -fl "appium.*server" || echo "no appium server process"
+   ```
+   - Verify no leftover Appium server process (Terminal B, Windows PowerShell):
+   ```powershell
+   if (Get-CimInstance Win32_Process | Where-Object { $_.CommandLine -match 'appium.*server' }) {
+      Get-CimInstance Win32_Process | Where-Object { $_.CommandLine -match 'appium.*server' } | Select-Object ProcessId, Name, CommandLine
+   } else {
+      "no appium server process"
+   }
+   ```
+
+9. **Agent completion criteria**
+   Mark the skill complete only when all are true:
+   - `appium driver list --installed --json` includes `uiautomator2` (fallback to `appium driver list --installed` if `--json` is unsupported)
+   - `appium -v` succeeds
+   - `appium driver doctor uiautomator2` reports `0 required fixes needed` (optional warnings are allowed)
+   - task result includes the doctor summary line with required/optional fix counts
+   - `environment-setup-android` completion criteria are satisfied
+   - task result includes connected-device output (`adb devices -l`) and emulator inventory (`emulator -version`, `emulator -list-avds`)
+   - task result explicitly states whether emulator preparation was skipped (and why)
+   - `/status` check returns a successful status response (`curl` on macOS/Linux, `Invoke-RestMethod` retry loop recommended on Windows)
+   - Appium server logs show startup/readiness successfully after the status check, or (if banner logs are unavailable) readiness is confirmed by `/status` plus JSON driver listing that includes `uiautomator2`
+   - If logs are available, `Available drivers:` includes a `uiautomator2` entry
+   - Appium smoke-test server process is cleanly stopped after validation
+
+## Constraints
+- Always run `appium driver doctor uiautomator2` after each environment change.
+- Use global npm/Appium commands as the default execution mode.
+- Use `npx appium` only if the user explicitly asks for local execution.
+- Do not skip Android prerequisite validation; rely on `environment-setup-android` for source-of-truth checks.
+- Use shell-appropriate commands (`bash` for macOS/Linux, PowerShell/cmd for Windows).
+- Treat optional doctor warnings as non-blocking.
+- Ask the user before installing optional dependencies, and install them only when the user explicitly needs that capability.
+- Prefer deterministic CLI checks over assumptions.
+- If elevated privileges are required, pause and provide exact commands for the user to run.
+- Do not claim success until doctor and smoke-test checks are actually green.

package/src/resources/submodules/appium-skills/skills/environment-setup-xcuitest/SKILL.md

@@ -0,0 +1,153 @@
+---
+name: "environment-setup-xcuitest"
+description: "Set up and validate an XCUITest Appium environment on macOS"
+metadata:
+   last_modified: "Mon, 06 Apr 2026 00:00:00 GMT"
+
+---
+# appium-xcuitest-environment-setup
+
+## Goal
+Prepares a stable Appium XCUITest execution environment on macOS by validating Node.js and Appium installation, installing and validating Xcode toolchains, and iterating Appium doctor checks until doctor reports `0 required fixes needed`.
+
+## Decision Logic
+- If host OS is not macOS: stop and tell the user this skill only supports macOS.
+- If Xcode is missing or command line tools are unconfigured: install/configure them before continuing.
+- If current Node.js does not satisfy `engines.node` for both `appium` and `appium-xcuitest-driver`: install/upgrade Node.js to a compatible active LTS version.
+- If Appium CLI or `xcuitest` driver is missing: install them via Appium CLI.
+- Use global npm/Appium commands by default (`npm install -g appium`, `appium ...`).
+- Use local Appium commands (`npx appium ...`) only when the user explicitly requests local execution.
+- If the user explicitly requests media features that require FFmpeg: run `environment-setup-ffmpeg` before final validation.
+- If install returns "already installed", ignore the error and continue (or run driver update).
+- If `appium driver doctor xcuitest` reports missing dependencies: fix each reported dependency and re-run doctor.
+
+## Instructions
+1. **Prepare Node.js + npm environment on macOS**
+   ```bash
+   sw_vers
+   node -v
+   npm -v
+   ```
+   If `node` is missing, install a compatible active LTS release and re-run the commands.
+
+2. **Install Appium npm command and XCUITest driver**
+   ```bash
+   npm install -g appium
+   appium driver install xcuitest || appium driver update xcuitest
+   appium driver list --installed --json || appium driver list --installed
+   ```
+   Prefer `--json` output for machine-readable verification. Confirm an `xcuitest` key is present; only fallback to plain-text output when `--json` is unsupported.
+   If the install command fails only because `xcuitest` is already installed, continue and do not stop preparation.
+
+3. **Validate Appium npm commands and Node compatibility (after driver setup)**
+   ```bash
+   appium -v
+   appium driver list --installed --json || appium driver list --installed
+   npm view appium engines --json
+   npm view appium-xcuitest-driver engines --json
+   ```
+   If current Node.js does not satisfy the reported `engines.node` ranges, install/upgrade Node.js to a compatible active LTS version and re-run the setup checks.
+
+4. **Verify Xcode command line setup and license**
+   First validate Xcode availability:
+   ```bash
+   xcodebuild -version
+   ```
+   If version info is returned, continue without changing `xcode-select`.
+   If version info is not returned, check the selected developer path:
+   ```bash
+   xcode-select -p
+   ```
+   If the selected path does not contain `Contents/Developer`, try setting it to the default Xcode app path:
+   ```bash
+   xcode-select --switch /Applications/Xcode.app/Contents/Developer
+   ```
+   Re-validate:
+   ```bash
+   xcodebuild -version
+   xcode-select -p
+   ```
+   Then ensure license and first-launch tasks are complete (use privilege escalation only if prompted/required):
+   ```bash
+   sudo xcodebuild -license accept
+   xcodebuild -runFirstLaunch
+   ```
+
+5. **Optional helper tools**
+   Install additional iOS helper tools only if the user explicitly requests capabilities that require them.
+   - For FFmpeg-related capabilities, run `environment-setup-ffmpeg`.
+
+6. **Run Appium doctor for XCUITest and fix in a loop**
+   ```bash
+   appium driver doctor xcuitest
+   ```
+   Use `0 required fixes needed` as the pass/fail gate. Optional warnings are non-blocking. Resolve required fixes, then re-run until this gate is met.
+   For deterministic automation, parse the doctor output for that exact phrase instead of relying on visual formatting.
+   `applesimutils` warnings are optional for basic simulator session creation, but recommended when you need permission-management helper APIs.
+   Bash gate example:
+   ```bash
+   DOCTOR_OUT="$(appium driver doctor xcuitest 2>&1)"
+   echo "$DOCTOR_OUT" | grep -q "0 required fixes needed" || { echo "$DOCTOR_OUT"; exit 1; }
+   echo "$DOCTOR_OUT" | grep -E "0 required fixes needed|optional fix"
+   ```
+   PowerShell gate example:
+   ```powershell
+   $doctorOut = appium driver doctor xcuitest 2>&1 | Out-String
+   if ($doctorOut -notmatch '0 required fixes needed') { throw "Doctor required fixes remain" }
+   $doctorOut | Select-String '0 required fixes needed|optional fix'
+   ```
+   AI-assisted fallback (only if exact phrase matching is inconclusive due output-format changes):
+   1. Re-run doctor once and capture full output (`appium driver doctor xcuitest 2>&1 | tee /tmp/appium-doctor-xcuitest.log`).
+   2. Ask an AI agent to classify required vs optional findings from the captured output.
+   3. Accept a pass only when the output clearly indicates zero required issues (for example: no required-fix section and no required-check failures).
+   4. If still ambiguous, mark status as `needs-manual-review` and do not mark the skill complete.
+
+7. **Optional simulator readiness preflight**
+   Before smoke testing, you may verify simulator availability to reduce false failures in session creation:
+   ```bash
+   xcrun simctl list devices
+   ```
+   If required by your flow, boot a target simulator before session creation.
+
+8. **Start Appium server smoke test**
+   ```bash
+   appium server
+   ```
+   Keep this server process running in Terminal A.
+   In Terminal B, run:
+   ```bash
+   curl -s http://127.0.0.1:4723/status
+   ```
+   First confirm `/status` responds successfully from `curl`.
+   Then confirm readiness from server logs and ensure the `Available drivers:` block contains `xcuitest` (for example: `- xcuitest@10.23.3 (automationName 'XCUITest')`).
+   If startup banner logs are not available in your terminal integration, use this fallback verification path:
+   - `appium driver list --installed --json` includes `xcuitest`
+   - `/status` reports server readiness
+   After smoke validation, clean up the running Appium server:
+   - In Terminal A, stop the server with `Ctrl+C`.
+   - Verify no leftover Appium server process (Terminal B):
+   ```bash
+   pgrep -fl "appium.*server" || echo "no appium server process"
+   ```
+
+9. **Agent completion criteria**
+   Mark the skill complete only when all are true:
+   - `appium driver list --installed --json` includes `xcuitest` (fallback to `appium driver list --installed` if `--json` is unsupported)
+   - `appium -v` succeeds
+   - `appium driver doctor xcuitest` reports `0 required fixes needed` (optional warnings are allowed)
+   - task result includes the doctor summary line with required/optional fix counts
+   - `curl -s http://127.0.0.1:4723/status` returns a successful status response
+   - Appium server logs show startup/readiness successfully after the curl check, or (if banner logs are unavailable) readiness is confirmed by `/status` plus JSON driver listing that includes `xcuitest`
+   - If logs are available, `Available drivers:` includes an `xcuitest` entry
+   - Appium smoke-test server process is cleanly stopped after validation
+
+## Constraints
+- This skill is macOS-only; do not provide Linux/Windows alternatives.
+- Use global npm/Appium commands as the default execution mode.
+- Use `npx appium` only if the user explicitly asks for local execution.
+- Always re-run `appium driver doctor xcuitest` after every fix.
+- Treat optional doctor warnings as non-blocking.
+- Ask the user before installing optional dependencies, and install them only when explicitly needed.
+- Do not skip Xcode license and first-launch checks.
+- If privileged commands are required, pause and provide the exact command for user execution.
+- Do not report readiness until doctor and smoke tests pass.