# Timer evidence procedure

Environment: web dev application, Chromium, 1280 x 800 CSS pixels, light theme. Each side runs from its own worktree with T3CODE_DEV_SEED=0 and its own freshly created database. Synthetic project and replay data only.

1. Apply seed-replay.py to each worktree. It replaces only the question and approval replay transcripts with identical synthetic ACP frames.
2. Add a project titled Timer evidence using the server CLI.
3. Pair the browser with the isolated dev server. Hide the sidebar and thread details.
4. Start recording and invoke window.t3dev.replay('question') or window.t3dev.replay('approval').
5. Leave the blocking request unanswered for at least 60 seconds.
6. Question: choose Summary (the single question submits automatically). Approval: approve once.
7. Record the resumed Working for timer throughout the forty-second synthetic workload and the completed Worked for summary.
8. Repeat on the other commit with the same transcript and viewport. Trim setup chrome from recordings; do not alter playback speed or timer pixels. The question clips begin after the sidebar and details close. Mobile clips crop the top 220 pixels containing the private environment label; the complete timer, request controls, and final reply remain visible.

The driver emits real protocol events through the dev replay provider, real adapter, orchestration, and clients. It does not mock timestamps or calculate durations for the application. No real provider account is used.

Mobile: leased Pixel 9 Android emulator, 1080 x 2424 physical pixels, light theme, T3 Code dev client. The same native fingerprint is used on both commits; JavaScript bundles are built separately by Metro from each worktree. Pair with the respective isolated backend, open the replay approval thread, leave it unanswered for at least one minute, tap Allow once, and record the resumed floating timer through the completed run fold.