# Forgejo link fixture

Run Forgejo 11 on port 3937 with `INSTALL_LOCK=true`, `ROOT_URL=http://localhost:3937/`, and SQLite. Create an administrator named `alice` with email `alice@example.invalid`, using a throwaway password in `FORGEJO_TEST_PASSWORD` and `--must-change-password=false`.

Run `python3 seed.py` to create the public `alice/demo` repository, a `feature` branch with two one-file commits, and pull request 1 into `main`. The script prints the first commit SHA; set the scenario's `sha` constant to that value when recreating the fixture.

Download tea 0.16.0 and authenticate it against `http://localhost:3937` using `tea login add --name scenario --url http://localhost:3937 --user alice --password "$FORGEJO_TEST_PASSWORD"`. Keep the tea config in an isolated directory. Make the real tea binary available to the app. In this run a `tea` launcher in the scenario checkout's `node_modules/.bin` scoped `XDG_CONFIG_HOME` to tea only:

```sh
#!/bin/sh
XDG_CONFIG_HOME="$FORGEJO_TEA_CONFIG" exec "$FORGEJO_TEA_BINARY" "$@"
```

Run the scenario with `T3CODE_DEV_SEED=0`, and `T3_SCENARIO_INHERIT_ENV=FORGEJO_TEA_CONFIG,FORGEJO_TEA_BINARY,T3CODE_DEV_SEED`. Set the two `FORGEJO_TEA_*` variables to the isolated config directory and real binary. `scenarios:prove` creates fresh application databases, pairs Chromium, seeds a project and a Replay Showcase thread, and executes the same link clicks on both commits. No real account or paid agent is used.

The app labels its commits list tab **Timeline** on these revisions. The first commit changes only `greeting.txt`; the complete pull request also includes `farewell.txt`.
