# Manual real-app comparison

Base: 8b633d9a9e54d9e580f6e77540a04bb87cf2da78
Head: b4c3b11cbdfadcb1c3522b907f5af2d334ca4007

Linux web client in Chromium, 1280x900 CSS pixels, device scale 2, light theme. Each checkout ran its own `T3CODE_DEV_SEED=0 vp run dev`, fresh database created by that revision. No live database was copied. Synthetic credentials are deliberately invalid; authentication success is not being tested. Stored-secret markers, saved host lists, and email fields show persistence.

Start the app once and stop it. Run `python3 seed.py <isolated-T3-home>` while stopped. The fixture uses projectSettingsFolded:true, retired Bitbucket email/accessToken and GitHub github.com token markers, with both old token files mode 000. Start again; both copies warn and fail.

Run three independent cases, restoring this fixture while stopped before each case. Remove any destination token files produced by a preceding case before reseeding: source-control-Yml0YnVja2V0-YWNjZXNzVG9rZW4.bin and source-control-Z2l0aHVi-dG9rZW5z-Z2l0aHViLmNvbQ.bin (only in this isolated test home).

1. Open Settings > Source control and enable Automatically pull. Stop the app, chmod both legacy token files to 600, restart. Select the test environment in the environment scope, expand Bitbucket and GitHub. Base: email empty and both tokens Not set. Head: me@example.com and both Stored secret markers.
2. Fresh fixture. Select the test environment, expand Bitbucket, replace Atlassian account email with new@example.com and press Tab. Let the save finish. Stop, chmod both old token files to 600, restart, expand Bitbucket. Base: new email, token Not set. Head: new email plus Stored secret marker. The head accepts the edit and preserves pending data; it does not reject it or silently discard the email.
3. Fresh fixture. Select the test environment, expand GitHub. Set Host to ghe.example.com and enter a synthetic new token, click Save. Stop, chmod both old token files to 600, restart, expand GitHub (default host github.com). Base: Not set for github.com; Saved for ghe.example.com only. Head: Stored secret for github.com; Saved for github.com, ghe.example.com.

Browser actions used preview navigation, click, fill, Tab, recording, and screenshots against these actual apps. Stills were accepted only after two screenshots at least 500ms apart matched byte-for-byte in pixels. Final evidence crops align the relevant host rows; GitHub clips show the settings content and exclude unrelated accounts. Browser privacy blur hides unrelated account identities. No settings-summary overlay was added.

Recordings cover the save interactions. Separate post-restart stills show their durable result; the toggle alone is visually identical and is not claimed as proof of retention. The app's token-verification messages refer to deliberately fake test tokens.

The fixture cannot be expressed through t3.project/t3.thread: it needs on-disk retired keys and unreadable legacy secret files. This is why the manual path was used.

The current head changed the approach from the earlier capture: host edits safely proceed while migration data is retained. The PR body still describes the removed rejection guard and should be updated. This proof establishes removal of data loss, not a host-creation rejection UI.

Not covered: per-kind retirement/clearing when one host migrates successfully while the other remains unreadable; API-token variant, multiple legacy GitHub hosts, native clients, real OAuth/network authentication.

Performed by GPT-6.1 Sol through Codex in T3 Code. No code modifications, commits, pushes, or forge writes.
