weichenandCursor ef66bfb331 Reject a rebuilt lock even when its inode is reused ...

Why: deleting the lock and creating a new file can recycle the same inode, so an inode-only check treated the rebuilt lock as the original.
Evidence: SELF go test ./internal/instanceguard ./internal/store ./internal/app, including TestClearedLockRecordRefusedWhenInodeStays.
Impact: instance_guard and the lock file now share a random lock_gen. A missing or different generation refuses Bind unless adopt.
Refs: docs/recovery/u8-sqlite-instance-guard.md
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-10-12 15:07:29 +00:00

..

guard_other.go

Reject a rebuilt lock even when its inode is reused

2026-10-12 15:07:29 +00:00

guard_test.go

Reject a rebuilt lock even when its inode is reused

2026-10-12 15:07:29 +00:00

guard_unix.go

Reject a rebuilt lock even when its inode is reused

2026-10-12 15:07:29 +00:00

guard.go

Reject a rebuilt lock even when its inode is reused

2026-10-12 15:07:29 +00:00