Record iPhone Duo verification of 0.2.0 on iOS 27.1

[janicduplessis]

Adds docs/verification/duo-0.2.0-ios-2026-09-23.md, a simulator run of 0.2.0 on an iPhone Duo with iOS 27.1. Nothing contradicted the 0.2.0 docs.

What it establishes:

• Division at 130° in Full screen, Shift 40, Inset 24 and Content box. Shift 40 reports the division at x 415.5 (Full screen minus 40) with unchanged provider bounds, so the origin-only re-measure from Re-measure iOS regions when the provider moves without resizing #17 runs.
• Unclipped frames. Content box reports the division at y −180 with its full 669-point height; the occlusion that no longer intersects is omitted.
• Hinge-driven refresh. At 180° the division disappears and it comes back when folded to 130°, with the provider staying 903 × 545. Both updates were dispatched 2 ms after a hinge update.
• Only the first event is synchronous (Deliver only the first iOS region event synchronously #25). The native log shows one experimental_flushSync dispatch at mount, then 12 dispatchUniqueEvent dispatches. After every step the screen showed the last dispatched payload.

How it was run

This Mac only has Xcode 26.6, so the run used a GitHub-hosted runner:

• xcode-27-xlarge, with Xcode 27.1 beta from the image and the iOS 27.1 runtime from xcodebuild -downloadPlatform iOS (no Apple account needed).
• A Release build of the example with the JS bundle embedded; agent-device 0.21.12 fold changes posture headlessly.
• Evidence (screenshots, snapshots, native log): run 35921251206.

The workflow, driver and temporary NSLog patch are only on the unmerged @janic/duo-verify branch; this PR adds just the doc. The standard xcode-27 runner (7 GB) stopped responding after booting the Duo in all three attempts; the doc lists this and other runner constraints.

Limits

Simulator evidence only. JS receipt of each event was not instrumented, so the event-delivery claim rests on the native dispatch path plus the final on-screen values.