# Terminal checkout branch-label proof Run each commit from its own installed checkout with a fresh, isolated T3 home and T3CODE_DEV_SEED=0. The included start-synthetic-app.ts is the current-main scenario startup harness with automaticGitFetchInterval set to zero in both the legacy setting and backgroundActivity override. Copy it over scripts/scenarios/start-app.ts in each scratch checkout, then run: T3CODE_DEV_SEED=0 node scripts/scenarios/start-app.ts web 127.0.0.1 node seed.mjs Pair the browser using the pairing-path file in that home. Use light appearance and a 1280x800 CSS viewport (captures have 2x device pixel ratio). For linked-checkout, the initial new-thread draft is already selected. Open the terminal using its toolbar button (the Cmd+J equivalent). Once its Terminal input is ready, run `export PS1='$ '; unset PROMPT_COMMAND; clear` to keep paths out of captures. Start recording, then run: git switch -c repro-linked-7409; git branch --show-current git switch linked-main; git branch --show-current Observe composer and Thread details after each command without refocusing or opening the branch picker. For the ordinary checkout, open the Terminal checkout sidebar thread, click New thread, choose checkout-demo, and open its integrated terminal. Prepare its prompt as above, start recording, then run: git switch -c repro-terminal-7409; git branch --show-current git switch main; git branch --show-current Base: both labels retain the initial branch after creation in both checkout types. Head: both update to the created branch, then return to the initial branch. Automatic fetching is disabled throughout. Stills were retained only after matching consecutive captures separated by at least 500ms. Recordings include the same create-and-return terminal interactions; observation dwell differs because the Browser panel was driven manually. No remote is configured, so PR and upstream metadata are not verified. AI-assisted; verified with the tests and tools listed above.