# Historical fork marker reproduction

Environment: Linux web client, Chromium, 1280 x 800 CSS pixels, light theme, device scale 2. Synthetic data only. Replay (dev), showcase recording. A deterministic title-command shim returns a title after 25 seconds; it replaces only the title model, not the server jobs, events, database, fork operation, or migration.

1. Check out f0ec7398d7 and install with `vp i`.
2. Run `python3 seed-title-repair.py <scratch-directory>`. Start `T3CODE_DEV_SEED=0 T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0 vp run dev --home-dir <scratch-directory>/legacy`.
3. Create a small git project with one README and an initial commit. Add it using `node apps/server/src/bin.ts project add <project-directory> --title "Title repair demo" --base-dir <scratch-directory>/legacy`.
4. Start a completed Replay showcase thread using `node apps/server/src/bin.ts thread start <project-directory> "Show the demo" --provider devReplay --model showcase --title "Source thread" --wait --json --base-dir <scratch-directory>/legacy`.
5. Pair the browser using the startup link. Open the returned thread by its environment/thread URL. Close the thread details panel.
6. Open the thread title actions and click Regenerate title. Immediately click Fork from this response. The fork inherits the active marker.
7. Wait for the source title to become Source title complete. Read the database to confirm the source job succeeded, the source marker is absent, the fork marker remains, and no title job belongs to the fork. No database writes are used.
8. Stop the historical server. Copy its synthetic home twice, into base and head homes. Each side starts from the same historical database. Do not copy a live or personal database.
9. Run base ac5dd1ff47d3d9d3807b9641d1b4b1cdf761c04f in its own checkout/home, and head e3ec6038d350d9115af4cefd7d0edcef27d289eb in its own checkout/home, both with T3CODE_DEV_SEED=0. Allow normal startup migrations.
10. On each side pair the browser, open the same fork by URL, close thread details if open, then right-click the fork's sidebar row. Base: dimmed fork and disabled Regenerating…. Head: normal fork and enabled Regenerate title.

Captures use the same viewport and light theme. Stills were taken after two matching screenshots more than 500 ms apart. The historical reproduction video is cropped to the left 980 CSS pixels to omit environment details; the base/head comparison videos show the full viewport. Before the base clip was trimmed, a failed selector lookup caused idle footage; the published clip starts just before the successful context-menu interaction.

Not exercised: historical subagent creation, other terminal outbox statuses, superseded request IDs, or startup preservation of pending/running matching jobs.
