Manual iOS proof driver. Use separate fresh base and head checkouts, each with dependencies installed. Start the isolated mobile scenario server/Metro helper with --no-seed; use distinct ports and T3 homes. Install the matching cached development client through mobile:install. Pair and open the synthetic thread before recording.

seed.ts CHECKOUT SERVER_PORT creates the same synthetic replay project/thread. pair.py CHECKOUT SERVER_PORT SESSION DEVICE_REACHABLE_HOST pairs it. core-driver.py CHECKOUT SESSION NEW_OUTPUT_DIRECTORY start records the successful first photo and failed second photo; invoke the same command with finish to expand, remove the successful photo, collapse to the failed compact thumbnail, restore permissions and retry. The recording spans both phases.

prepare-question.py CHECKOUT changes only the replay fixture from a constrained enum to a free-text question so QuestionAttachments renders. Let the server reload, then question-seed.ts CHECKOUT SERVER_PORT creates it. Open Attachment question, then question-driver.py CHECKOUT SESSION NEW_OUTPUT_DIRECTORY records failed upload and retry. Both commits use the identical fixture.

Devices: iPhone 18 Pro, iOS 27.2, portrait 402x874 points, default light theme, stock synthetic photo library. The picker has an unreliable accessibility tree, so the driver waits for the known flower-photo grid in screenshots before tapping the first or second photo and its confirmation control. Attachment failure comes from chmod 555 on the isolated attachments directory, restored to 775 for retry.

The scenario attempt stopped before completing after three navigation/picker/keyboard corrections; no passing automated proof.json is claimed. The reported proof uses the manual fallback. Base composer recording was completed in two execution segments after its screenshot-stability loop was interrupted; the UI interaction sequence matches head. Expanded composer and question-answer detail crops exclude unrelated status/elapsed-time indicators.
