# Activity time-order proof

The seed and scenario use synthetic data only. Authenticate `glab` and git to GitLab first.

1. Run `python3 seed.py > fixture.json`.
2. Place the scenario beside `scripts/scenarios/t3-mobile.ts` in a current main checkout and run `vp i`.
3. Set `actionTimeout: 120_000` in `scripts/e2e.config.ts` so pooled-device installation has enough time.
4. Run `SCENARIO_FIXTURE_FILE="$PWD/fixture.json" T3CODE_DEV_SEED=0 T3_SCENARIO_INHERIT_ENV='SHELL,T3CODE_DEV_SEED,GLAB_*,GITLAB_*' vp run scenarios:prove scripts/scenarios/pr-28391-time.e2e.ts --base b28dc0eb1d8ac4b95292bdfc95ea2a3f9ad2600b --head d992747cb48f35300a40b6e23c5f0862277194d2 --upload-command 'ghdrop upload'`.
5. Delete the synthetic GitLab project using the projectId printed in fixture.json: `glab api projects/<projectId> -X DELETE`.

The commit's author and committer dates are two hours before fixture creation, represented with UTC+14. GitLab assigns the later comment's UTC date. The app is driven through its real Pulls list and merge request Activity tab; the single assertion compares the displayed row positions in both sort directions.
