Epic: bring the iOS app current, with its own world and verification #3

Story

As the owner, I want the iOS app brought current and tested in its own world, so that the features only the app can show are proven the way the web features are.

What I'd notice

The iOS rows leave the web feature map and have their own map and their own checks. Nothing changes in the app until the first batch ships.

Context

• The web features are proven through the screen by hermetic Playwright specs against eve and a fake relay. A native app cannot be driven that way.
• The devbox has Xcode and an iOS simulator runtime, so a simulator is available. No door builds this app, boots a device and drives it.
• Eight rows in eve's feature map run only in the native app: G9.22, G9.23, G9.25 and G15.4 to G15.8, plus G15.1 r3. They are being moved to docs/FEATURES-iOS.md in the eve repo (see eve#310 and eve#369).
• The app has not been touched for a while. The first batch checks that it still builds and signs in.

Acceptance criteria

1. The app builds on the devbox with the current Xcode.
2. The app signs in against a hermetic eve through the passkey sheet.
3. Each row in docs/FEATURES-iOS.md names its door, its journey or "manual device pass".
4. A simulator journey proves each row that a simulator can show.
5. A row that needs a device (screen lock, haptics) is listed as a manual device pass with its steps.
6. The simulator journeys run through devboxverify as their own world.
7. A PR to this repo runs only the iOS checks its change reaches.

Batches (children are filed when the epic is scheduled)

Out of scope

• Real-device automation.
• New app features.

Notes

• Deferred by the owner on 2026-10-10: approved, not scheduled. Do not start.
• The web phone layout is covered separately in eve by specs at a phone-sized viewport.