[shaynelegault]

Adds the native P105 adapter for the first-generation iPad mini Wi-Fi (iPad2,5, P105AP). Orchard can boot a verified private RAM bundle through the owner's iOS jailbreak and then hand off to an existing USB/NFS export.

The adapter binds the selected iOS device to its saved ECID and checks the live Linux boot identity through re-enumeration. It records each boot mutation before sending it, resumes a saved iBEC cable wait, provisions pinned diagnostics and scopes the host USB address to the selected device. An authenticated NFS handoff preserves the diagnostic connection and RAM rescue console.

The shared adapter/protocol changes retain the J71b interface and add explicit P105 boot/firmware policy. New p105-manifest, owner-input capture and network-cleanup commands support the private preparation flow. The package and build workflow pair CLI 0.1.11 with hardware 0.1.11. README changes add the P105 link.

Validation

The merged suite passes 225 tests on Python 3.9.6 and 3.14.6. Mypy passes across 15 source files. Fixtures cover ambiguous discovery, target changes, boot continuation and uncertain upload outcomes. Physical qualification covers the Wi-Fi P105; J71b has coverage through the existing suite.

The installed CLI completed two current native Omarchy A boots while Python audit hooks denied reads from all five source checkouts and the earlier workspace. Both reached the new NFS desktop with zero failed system or user units. The rescue shell was verified in RAM, and saved Wi-Fi plus LAN SSH worked after reboot. The owner confirmed Home, Omacalc and on-screen keyboard entry of a Wi-Fi password.

Dependencies and current limits

• Hardware and recovery runtime: Add experimental P105 iPad mini 1 hardware and recovery support orchard#10
• ARMv7 recovery composition: Add ARMv7 P105 recovery composition for tethered boot minimal-linux#3
• Native desktop and current device results: Build native ARMv7 Omarchy desktops for iPad mini 1 omarchy-a#6

Review the hardware dependency first. The default packaging job downloads hardware tag v0.1.11. Before that release exists, a maintainer can use the workflow's hardware_run_id input to pair with the tested hardware workflow artifact. The automatic PR packaging path depends on that hardware release being available.

The qualified path uses macOS, trusted iOS SSH access and owner-prepared firmware/calibration. The host serves NFS throughout the desktop session. Internal installation and untethered startup require later storage/boot work. Touch latency and the earlier intermittent calibration failure remain open. Reproduction and host prerequisites are in docs/p105.md.

[shaynelegault]

restructuring PRs to follow https://github.com/OrchardLinux/hardware/blob/main/CONTRIBUTING.md