Environment: Pixel 9 emulator, Android API 36, en-US, portrait 1080x2424, light theme. Each commit used its own checkout, Metro bundle and fresh isolated server database; Replay (dev), multi-turn recording. No live data was copied.

1. Use seed.py with checkout and isolated home arguments. It creates Clock format demo and starts Android clock format with Hello timestamp check through the app CLI and Replay.
2. Pair the installed development client with that server. Open Android clock format with the system in 12-hour mode and UTC.
3. Start whole-device recording. Open Android Settings Date & time, enable Use 24-hour format, return to T3 Code without relaunching. Capture existing timestamps.
4. Relaunch T3 Code, reopen the thread, type Second message in 24h mode, press Send, and capture the user message and Replay reply. Stop recording.
5. Switch back to 12-hour mode and return. Run clock-interaction.py with output directory and session arguments to record changing back to 24-hour mode with both existing user and assistant rows visible.
6. For midnight formatting, turn Automatic time zone off, choose Time zone > Select UTC offset > GMT-05:00. Relaunch the app and reopen the thread. Messages created before 06:00 UTC are now local 00:xx. Capture them in 24-hour mode.

stable-capture.py captures two screenshots at least 500 ms apart and requires identical pixels before accepting the still. Recordings were inspected through extracted contact sheets.

The initial CLI message is displayed as an Agent context chip. The second message is entered in the mobile composer and visibly tests both user and assistant timestamps.