PR #28575 real dev verification, 2026-11-01, Linux Boat VM
main: 8760d063e903406c8e8f695b0852c0a15fc1e00f
PR: c63e30b009b936cd9c1a74de9e2ec468e8739c57
Playwright 1.60.0, /usr/bin/google-chrome, 1280x800.
Project /home/user/branch-check was added through the web app.
Branches verify/branch-a and verify/branch-b were created through its branch pickers.
Real Codex gpt-6.1-sol turns, no replay provider or mocks.

main create-ref events:
main -> verify/branch-a (pending) -> main (enabled) -> verify/branch-a
main switch-ref events:
main -> verify/branch-a (pending) -> main (enabled) -> verify/branch-a

PR switch-ref events:
main -> verify/branch-a (pending) -> verify/branch-a (enabled)
6 more settled switches: 0 label reversals; git branch --show-current matched every target.
PR draft composer create-ref: verify/branch-b; both composer and details agreed.
Real provider response: branch: verify/branch-b; checkout is clean.
Real provider checkout: git switch main succeeded; branch: main; status: clean.
Details label followed the external checkout to main.

Separate pre-existing limitation reproduced on both main and PR:
after a provider switches to main, selecting the previously current branch can use stale
worktree metadata and leave git on main. Reloading refreshes that branch list.
This is outside the label-flip change and was left untouched.

blacksmith-check: vp run check:changed b50d8a1b15eed3a75e1e0969765e14c6436d80d7
PASS format, lint, knip (2 parts), graphql, affected typechecks (4 packages),
53 focused tests in 4 files, React Compiler coverage of 2 changed files.
Remote source snapshot history was reconstructed against the exact PR base for this check;
no app source changes were needed.
Cafe CI: 29 successful, 0 failing, 0 pending at verified head.