Refresh the Flutter snapshot: LAUNCH.md and the iPhone verification pass

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

rippr-flutter-src/docs/port/PROGRESS.md

@@ -797,3 +797,36 @@ tests the project has ever had.
 
 **What remains is not code.** It is a rider, two phones, and
 [REAL-RIDE-CHECKLIST.md](REAL-RIDE-CHECKLIST.md).
+
+
+---
+
+## iPhone verification pass
+
+Scoped and executed: [IOS-VERIFICATION.md](IOS-VERIFICATION.md).
+
+**An assumption was attacked and survived.** `simctl location start --speed=15`
+interpolates between waypoints over time — unlike Android's teleporting `geo fix` — which
+looked like it might make speed testable locally at last. A probe captured 8 fixes, every
+one reporting **0.0 m/s**. So "no simulator produces velocity" holds on iOS too, and the
+real-ride checklist remains mandatory.
+
+A full ride was recorded on the simulator through the real UI:
+
+```
+trip=1 points=18 distanceM=245.5 maxSpeedKmh=0.0 movingMs=0 segments=1
+```
+
+245 metres of travel with **zero moving time** — correct behaviour given speed is pinned
+at zero, and a compact illustration of exactly what local testing cannot reach.
+
+Also confirmed visually on iOS: the record screen renders correctly, and the location
+permission dialog displays the specific usage string written for Guideline 5.1.1.
+
+`integration_test/ride_simulation_test.dart` is kept — it is a reusable local
+verification, not a throwaway.
+
+**Named gap:** no screenshot of the iOS trips list or detail screen. Both are verified
+functionally, but tapping the iOS simulator is not scriptable the way `adb shell input
+tap` is, and a fresh install re-prompts for location over the UI. Android's equivalents
+were checked visually.