CLI proof for pull request 24963 Base: c00a373491d20ebcef901b81170abfb9f5f757fe Head: 3f9141227ee681be346cf9bd1caf5c75d8c2c3cd Linux x86_64, Node v26.12.1. Both worktrees installed with vp i. Real CLI executed as node apps/server/src/bin.ts from its checkout. No mock or test harness replaces server or doctor. Run: python3 compaction-driver.py before python3 compaction-driver.py after python3 holder-driver.py before python3 holder-driver.py after Each side starts its own fresh database using the real server. No live T3 data is copied. Compaction seed: eight projects with synthetic 8-MiB script bodies sent through /api/projects/mutate; resulting database 129.0 MiB. The storage PRAGMA auto_vacuum=NONE and VACUUM reproduce a pre-compaction database, without changing schema or migration history. Doctor is SIGSTOPped at its rewrite output to make the concurrent launch deterministic, then SIGCONTed after that launch exits. The same driver and timing control are used on both commits. Base launch exits 1 with database is locked; head launch exits 78 with ServerAlreadyRunningError. Doctor subsequently completes successfully on both sides. The holder check uses a separate fresh 880-KiB database in storage mode NONE, starts the real manual server, waits for its readiness output, records its actual PID, then runs doctor --fix. Base gives generic instructions; head identifies the matching live PID and states the background service did not start it. The server is verified still live after doctor exits. MP4s are timestamped terminal renderings of captured stdout and driver actions at original relative timing (initial seeding omitted). Stack frames are omitted from videos for legibility. Full sanitized transcripts are included. Absolute paths are replaced with placeholders; pairing credentials and private metadata are never published. Video dimensions: 1600x1050; fixed dark theme and font on both sides. PNGs are the final video frames, supplied as table thumbnails rather than standalone screenshot proof. Not exercised: desktop launch, installed background-service stop/restart, legacy service compatibility, or the race after repair releases ownership before a service restarts. Uncontrolled compaction timing was not measured. AI-assisted; verified with the tests and tools listed above.