iOS E2E

Verify TrueSheet's native iOS behavior on the simulator with evidence, not eyeballing. Every claim — "fixed", "regression", "pre-existing" — should come with a frame trace, an event log, a debug log line, or an A/B result against HEAD.

Follow AGENTS.md: build only when the user asked for builds or e2e. Read argent-device-interact before driving the simulator.

When to use

• A change in ios/ needs to be built and exercised on the simulator, or reviewed for regressions.
• Something visibly misbehaves: a sheet or footer jumps, flickers, or lands at the wrong height.
• Event or timing correctness: onPositionChange realtime vs settled, detent changes, props applied (or lost) around present, dismiss, cancelled swipes, or stacked sheets.
• A bug report needs classifying as a regression or pre-existing by comparing against HEAD.

1. Build, install, launch

Bare example (example/bare, bundle id truesheet.example). Native library changes need a rebuild; JS changes hot-reload through Metro.