Find the right iPhone DeviceSupport candidate

Resolve bundled files from this skill root. Use filsv/iOSDeviceSupport and iGhibli/iOS-DeviceSupport as third-party legacy-image inventories, not authorities guaranteeing Xcode compatibility.

Step 1: Identify the device and the actual failure

1. Record the connected device's exact ProductVersion and BuildVersion, selected Xcode version/build and developer directory, macOS version, and first relevant prepare/install/debug error. A model name or iOS major alone cannot select a support image.
2. Read references/compatibility-installation.md before proposing a repair. Compare Apple's Device Support range for that Xcode, not its SDK, deployment target or simulator range. If the device OS was genuinely dropped, prefer a supported older Xcode plus compatible macOS/host; copying a DDI cannot restore a removed protocol stack or official support.
3. Distinguish trust/pairing/locked-device or USB failure from a missing legacy image, modern image personalization, or signing/build error. Follow normal user-reviewed trust/Developer Mode setup; do not bypass approval or modify global Xcode settings.
4. Identify the selected installation with the session's DEVELOPER_DIR or xcode-select -p; verify xcodebuild -version under that selection. Never assume /Applications/Xcode.app when beta/older Xcodes coexist. Do not query or modify the wrong Mac in remote workflows.

Gate: exact device OS/build and actual Xcode support-range/failure classification are known. Any missing Mac/device evidence remains explicit.

Step 2: Look up the actual inventory