ada3c28d45
Both destructive restore paths (_safe_restore_db's unlink+move fallback and update_cmd._restore_state_db_from_snapshot) guarded only against FOREIGN holders via _foreign_db_holder_pids(), which excludes the calling process by design. A live tracked connection in the same process (the agent's own SessionDB during /snapshot restore, a read-pool handle, a second SessionDB instance) was unprotected: the swap unlinked state.db and its -wal/-shm under it, leaving the process on deleted-inode fds — the #90837/#90950 split-brain fingerprint, produced first-party. Proven live on main via /proc/self/fd (state.db-wal (deleted) ghosts after both paths ran under a tracked connection). Run the destructive swap inside sqlite_safe_read.offline_file_access(), which fails CLOSED on any tracked in-process connection and holds the connection-lifecycle lock across the whole swap so no new connection can appear mid-replace. Holder-free restores are unchanged (control verified: restore succeeds, stale sidecars cleared). Part of the #90837 sidecar-unlink audit (wave 6).