weichenandCursor 1f7bcac6e0 Keep the activity lock from creating or aliasing the database ...

Why: Review found that a missing data directory failed before open, adopt recreated a missing database, a lock symlink could be written as the database, and a failed identity check stored the wrong instance id.
Evidence: SELF go test TestMissingDataDirIsCreatedBeforeLock, TestLockSymlinkCannotAliasDatabase, TestAdoptDoesNotCreateMissingDatabase, TestIdentityFailureDoesNotStick.
Impact: First start creates the data directory before taking the lock. Adopt still refuses a missing database. The lock file is opened with O_NOFOLLOW and rejected when it is the database. Identity is checked before the guard row is written.
Refs: docs/recovery/u8-sqlite-instance-guard.md
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-10-12 14:16:55 +00:00

..

guard_other.go

Refuse a second SQLite service before migration

2026-10-12 13:53:42 +00:00

guard_test.go

Keep the activity lock from creating or aliasing the database

2026-10-12 14:16:55 +00:00

guard_unix.go

Keep the activity lock from creating or aliasing the database

2026-10-12 14:16:55 +00:00

guard.go

Keep the activity lock from creating or aliasing the database

2026-10-12 14:16:55 +00:00