PR 30066 runtime verification, Linux Boat VM, 2026-11-03 main: cefb544af3c98224874419198c0359b652ca3c94 PR: bd21af04329eb260e62b154147843ccd02c2acf4 V1 app: 024d49520eadb24cc2f2cef0b0a82c33f0290813 Data created through the actual web app with Playwright and /usr/bin/google-chrome: Added /home/user/t3code as a local git project, created a thread, selected Codex gpt-6.1-sol, completed LEGACY_IMPORT_OK and a read-only git ls-files inventory turn returning REPO_INVENTORY_OK. No fixture SQL or mocked provider. Stopped V1 server, copied its userdata into separate main/PR homes. Ran one dev server at a time, background processes with captured PIDs. $ sha256sum source state.sqlite and main/PR input copies All three: f866b374e4e2659fb598b9ce9f13c37e78e2db4a7eb6d814a97425b63c6d32e3 Hashes still identical after both imports and PR restart. $ PRAGMA auto_vacuum; PRAGMA page_count; PRAGMA freelist_count; PRAGMA integrity_check; Read-only inspection of the actual running server database using node:sqlite: V1 source: mode=0, pages=606, free=0, integrity=ok, migration=54 main startup: mode=0, pages=746, free=256, integrity=ok, migration=78 main 12:00:41: mode=0, pages=746, free=524, integrity=ok PR 12:01:15: mode=2, pages=747, free=255, integrity=ok, migration=78 PR 12:02:16: mode=2, pages=247, free=0, integrity=ok PR 12:02:46: mode=2, pages=247, free=0, integrity=ok The app background maintenance reduced PR page count by 500 (2,048,000 bytes). No direct VACUUM, PRAGMA writes, doctor repair, or accelerated timers were used. Main and PR both displayed the migrated transcript and inventory turn. PR completed a real continuation with PR_CONTINUE_OK. After restarting PR with the existing V2 database and original V1 still present, PR_CONTINUE_OK persisted, the V2 inode was unchanged, and another real Codex continuation completed PR_RESTART_OK. Integrity remained ok and mode remained 2. Blacksmith: vp test run apps/server/src/persistence/initializeV2Database.test.ts apps/server/src/persistence/DatabaseStorage.test.ts 6 tests passed. vp run check:changed cefb544af3c98224874419198c0359b652ca3c94 format, lint, both knip passes, GraphQL, 3 package typechecks, 5 tests passed. The Blacksmith snapshot needed a depth-2 fetch of the PR head to restore its merge-base ancestry before check:changed could run. GitHub checks: 31 successful, zero pending/failing at inspection. Unverified: macOS/Windows desktop, native iOS/Android, multi-GB imports, worker cancellation on Windows, and simulated crash/corruption scenarios. No source changes or pushes were needed.