AI-assisted; verified with the tests and tools listed above.

Reproduce with the scenario runner from [a0efdaeb89](https://github.com/pingdotgg/t3code/commit/a0efdaeb89) of [pingdotgg/t3code](https://github.com/pingdotgg/t3code).
Apply scenario-environment.patch at the repository root and place
git-actions-disabled.e2e.ts in scripts/scenarios/. The startup patch disables
automatic fetching, uses a synthetic terminal prompt, and labels the environment
with the actual app checkout's Git revision. It does not change production source.

Run:

    T3CODE_DEV_SEED=0 vp run scenarios:prove scripts/scenarios/git-actions-disabled.e2e.ts --base b3fdf2b10fb92e5dbc71a83381c602a8a464bbca --head f693214f6f5c9cc14eb02b0e6fd2cca870152d05

The same driver creates four synthetic repositories and one replay-backed thread
per repository on each side. The web viewport is 1280 by 800, light theme.
Repositories cover clean synchronized main, no remote, detached HEAD, and one
commit behind upstream. All remotes are local disposable repositories.

After inspecting these menus, the driver edits README.md through the in-app
terminal without changing window focus, tabs through the Git action group,
opens its menu, restores README.md, edits again, hovers the action group, and
physically clicks the chevron. Marker files under .git mark terminal command
completion. A capture is accepted only when consecutive PNGs 500 ms apart match.

Recordings omit startup pairing and teardown. No private database was seeded.
No production source changes are included or committed.
