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/restore.cgi
Site	DriftSense self-monitor on local
Kind	local
Captured at	2026-07-12 00:48:53
Captured SHA	2f8b971be093cae403df1885b6ed907b44aa158611a204e671fe3f1847f77343

Current state on disk

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

File present	yes
Size	16800 bytes
Current SHA	2f8b971be093
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.