Manual reproduction evidence Surface: real web client, Chromium, Linux, 1280x800 CSS viewport, device pixel ratio 2, light theme. Captures crop the sidebar (510x1600 physical pixels); stills are scaled to 255x800. Both sides use identical crops. Two separate screenshots of each final sidebar had zero differing pixels, with more than 500 ms between them. Base: 3a8c250cb0c8056f2f563091fd412fe5db809fa1 Head: 54a921941b1b3697381365efc8dfd1ffbecb21b8 The driver starts actual t3@0.0.45 and each checkout's actual server. No fixtures, tests, SQL writes, copied user data, or paid agent turns are used. Project directories are synthetic, and every run uses a fresh isolated home. Auto-bootstrap creates a project and an empty New thread. Preparation: - Install dependencies with vp i in each checkout. - npm pack @t3code/t3-linux-x64@0.0.45 and extract its package directory beside driver.py. - Create project-a and project-b directories beside driver.py. - Run python3 driver.py in an interactive terminal. - Each printed stage waits for Enter. Use each checkout's dev:web runner with an isolated --home-dir and --no-seed, pointing to its server port. Set T3CODE_DEV_SEED=0. Stages, identical on both sides: 1. Start V1 from project-a with --auto-bootstrap-project-from-cwd. Confirm project-a and New thread exist. 2. Enter: stop V1; launch V2 once, without creating V2 work. 3. Enter: stop V2; start V1 from project-b with the same home. Confirm V1 has projects A and B and their threads. 4. Enter: stop V1; launch V2. Base omits B. Head includes B, warns that the earlier copy has no V2 work, and retains statev2.sqlite.stale. 5. Record a browser reload, press Enter to restart the V2 server, reload again, and inspect the same sidebar. The missing/present B result persists. 6. Enter to stop the final server. The uploaded videos show the reload/restart observation on each side, not the entire setup lifecycle. The driver and startup/database observations document that lifecycle. Both browser shell API responses agreed with the visible sidebar: base one project/thread, head two projects/threads. The backup on head contained project-a only. Not exercised: messages, metadata updates, preservation of V2-authored work, revoked sessions, concurrent CLI writes, or failure recovery. AI-assisted; verified with the tests and tools listed above.