# Android snooze language reproduction

Base: [ba640037e8](https://github.com/pingdotgg/t3code/commit/ba640037e82dde3009d1b99573a20414c0dec89b). Head: [4a25fc2b36](https://github.com/pingdotgg/t3code/commit/4a25fc2b36473b4b4541f11f7b526be87c8fc50f).

Each commit ran from its own checkout, with installed dependencies, its own fresh T3 data directory, `T3CODE_DEV_SEED=0 vp run dev --host 0.0.0.0`, and its own Metro process. The Android development client had the same native fingerprint on both commits. Only one Metro process ran at a time. The application data was cleared between commit switches, then paired with the matching isolated backend. Synthetic data was created through the project and thread CLI, using the commands in seed.sh and the free devReplay provider. No installed application database was copied.

Device: pooled Pixel 9, Android API 36, portrait 1080 x 2424, light theme, UTC. Session used by the drivers: proof38663.

## French override

1. Android Settings > System > Language & region: English (United States).
2. Android Settings > System > Date & time: Use 24-hour format off.
3. T3 Settings > General > Language: Français. Relaunch and wait until French controls appear.
4. Open Général to show Langue: Français. Start recording here.
5. Run `python3 date-flow.py fr`: Chats; swipe the first idle thread partly left; choose Reporter; Personnalisé…; leave Date et heure selected; advance six months from November 2026 to May 2027; choose May 5.
6. Wait for a stable screenshot pair using stable-capture.py. Stop recording.
7. Start recording and run `python3 time-flow.py 12`: select the time button, PM, 2 o'clock, 30 minutes. Capture the stable 2:30 PM label. Stop recording.
8. In Android Settings turn Use 24-hour format on; return to the same open T3 dialog. Start recording and run `python3 time-flow.py 24`: choose 14 hours and 30 minutes. Capture 14:30. Stop recording.

The same date-flow.py and time-flow.py drivers were run against both commits. The initial base reproduction was also driven manually with the same steps; base-fr-scripted.mp4 is the repeated scripted run.

## System-language regional case

On both commits, set Android to English (United Kingdom), enable 24-hour format, choose T3's System default language, and relaunch. Record from General showing System default. Run `python3 date-flow.py en` and capture May 5. Both commits show 5 May, preserving the British regional order. The first base run used the US date accessibility selector and stopped at the final selection; the British selector was then used to select the same day. The uploaded driver includes that correction.

## What this proves

Under the requested French override, the date button changes from May 5 to 5 mai. The same clock choices produce 2:30 PM in 12-hour mode and 14:30 in 24-hour mode. System default preserves en-GB regional formatting in the tested case.

This does not show a fully French dialog: the native Android picker remains English, and the preceding snooze menu still uses Mon 9:00 AM under La semaine prochaine. The proof is about the requested app-owned button label, not overall mobile date consistency or maintainer endorsement of a localization policy.

Stills were accepted only after two full screenshots taken at least 500 ms apart had identical decoded pixels. Captures were visually inspected; video contact sheets and final frames were inspected before upload. Android screenrecord emits frames only when the display changes, so a video's final static hold can be shorter than the recording window.
