PR #24078 runtime verification, 2026-10-28, Linux / Node 24.22.1 main: f17c9d202b38ea9a009a2d6dc3932e212bad4c24 PR: 31d9e059690325d05519c54cc1af6d9f3c7e6698 Data origin: published t3@0.0.45, real web UI, a real git project at /home/user/doctor-verification, Codex gpt-6.1-sol through the local proxy. Legacy reply: DOCTOR_LEGACY_OK doctor runtime verification Stopped the old app and copied its app-created data into separate main and PR homes. Each dev app imported the legacy thread. No synthetic SQLite data or mocked provider. Only one app server ran at a time. MAIN baseline: $ node apps/server/src/bin.ts doctor --base-dir /home/user/main-legacy-data --fix Database: 876 KiB, 24 KiB reclaimable. Database from before 0.1.0: 4 KiB, kept for rolling back. Reclaiming database space. This can take several minutes... Done: 876 KiB -> 856 KiB, 0 superseded events removed. Legacy database and its WAL/SHM remained present. $ node apps/server/src/bin.ts doctor --base-dir /home/user/main-legacy-data [selected only "Delete the database from before 0.1.0" in the real terminal prompt] Deleted the database from before 0.1.0. Only statev2.sqlite and its sidecars remained. The Windows-only failure did not reproduce on Linux. PR baseline: imported history was visible in Chrome, and a new real turn returned DOCTOR_PR_BEFORE_OK doctor runtime verification $ node apps/server/src/bin.ts doctor --base-dir /home/user/pr-legacy-data --dry-run Database from before 0.1.0: 4 KiB, kept for rolling back. Dry run: nothing changed. $ node apps/server/src/bin.ts doctor --base-dir /home/user/pr-legacy-data --fix Database: 960 KiB, 0 KiB reclaimable. Reclaiming database space. This can take several minutes... Done: 960 KiB -> 956 KiB, 3 superseded events removed. Legacy database and its WAL/SHM remained present. Opened a real read-only node:sqlite connection to the app-created legacy database, read sqlite_master, and kept the connection open (69 schema objects). $ node apps/server/src/bin.ts doctor --base-dir /home/user/pr-legacy-data [selected legacy deletion in the real terminal prompt] DatabaseInUseError: Stop the T3 Code server and desktop app, including any version before 0.1.0, before repairing the database. Cause: database is locked $ sha256sum -c /tmp/legacy-before-refusal.sha /home/user/pr-legacy-data/userdata/state.sqlite: OK /home/user/pr-legacy-data/userdata/state.sqlite-shm: OK /home/user/pr-legacy-data/userdata/state.sqlite-wal: OK Closed the real reader. $ node apps/server/src/bin.ts doctor --base-dir /home/user/pr-legacy-data [selected legacy deletion in the real terminal prompt] Deleted the database from before 0.1.0. Legacy database, WAL and SHM absent. $ sha256sum -c /tmp/current-before.sha /home/user/pr-legacy-data/userdata/statev2.sqlite: OK SHA256: 0744061afc45f5fcabbc1d135e681ceb9bd9460626c7dc99f57c13ab9ee8cd90 $ node apps/server/src/bin.ts doctor --base-dir /home/user/pr-legacy-data --dry-run Database: 956 KiB, 0 KiB reclaimable. Nothing to repair. Restarted PR dev app using the same data directory. Chrome retained the migrated legacy conversation and the pre-cleanup turn. Submitted another real Codex gpt-6.1-sol turn in that same thread through the composer: DOCTOR_PR_AFTER_OK doctor runtime verification The real git project remained clean. Blacksmith: DatabaseMaintenance.test.ts and doctor.test.ts: 7 passed. Live GitHub checks: 22 SUCCESS, 17 SKIPPED, no pending or failing checks. No source modifications, commits, pushes, labels, merges, closes or rebases. LIMIT: this proves the real Linux CLI/client/provider flow and neighboring behavior. It does not reproduce the original Windows bug or prove native Windows deletion. The Windows-path unit tests are supporting evidence, not Windows runtime proof. Native Windows, macOS, Electron, iOS/Android and relay/tunnel were not exercised.