Restore

Restore file to captured state

Every captured change carries its SHA-256-addressed content in BLOB_STORE. Restoring writes that content back to the original path — current file gets backed up to <path>.drift_restore_backup_<epoch> before overwrite.

What will change

Preview -- nothing has been written yet.

Target file	/var/www/vhosts/3dshawn.com/site1/databases.cgi
Site	DriftSense self-monitor on local
Kind	local
Captured at	2026-07-10 18:57:29
Captured SHA	ff38817268ac90be3542deff997c203674668b08c2a0a2d205cc38e205124c0e

Current state on disk

Live check just now. If SHAs match, the restore is a no-op.

File present	yes
Size	2855 bytes
Current SHA	ff38817268ac
Same as captured?	yes -- no-op

See exactly what's different →

Confirm restore

Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.