fix iOS build blockers and add project scaffold

PLAN.md

@@ -13,6 +13,7 @@ This is the canonical working plan and progress log for the project. Use this fi
 - Backend smoke coverage was added for `server_time` and audit logging.
 - iOS now follows the backend-backed flow, syncs clock from `/health`, flushes analytics, and uses localized language labels instead of hardcoded `EN` and `SV`.
 - iOS source was updated for the backend-backed session and round flow, including the real preview cue points and localized session strings.
+- iOS settings now uses localized copy instead of a scaffold placeholder, and the screen is wired into the root scroll flow.
 - Android debug build passes with `./gradlew :app:assembleDebug`.
 - Backend tests pass with `cargo test`.
 - Backend localization bundles now have a contract test, and the localization catalog matches the shipped English and Swedish keys.
@@ -20,11 +21,13 @@ This is the canonical working plan and progress log for the project. Use this fi
 - Backend bet coverage now includes a direct regression for late-lock rejection.
 - Backend bet coverage now includes invalid-session and invalid-market rejection regressions, plus settlement override coverage.
 - Backend analytics coverage now includes a representative key user flow batch.
+- iOS project scaffolding now exists as `mobile/ios-app/HermesApp.xcodeproj` with a shared scheme and XCTest target.
+- iOS sources and tests typecheck against the iPhone simulator SDK, and a standalone localization/error-mapping harness passes.
 
 ### Still Open
 
 - Continue through the remaining plan phases and finish any leftover localization and polish work.
-- Add iOS build validation once an Xcode project is available in `mobile/ios-app`.
+- Run Xcode build/test validation once the local Xcode license is accepted; `xcodebuild` is currently blocked by the license gate in this environment.
 - Keep expanding tests around session, odds, settlement, and analytics behavior.
 
 ## 1. Purpose
@@ -1310,6 +1313,8 @@ Must support flags for:
 
 The AI agent must work in this order.
 
+After each major completed change set, create a git commit and push it before starting the next major change.
+
 ### Phase 1: Documents
 
 1. Write root README