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/_alert_dispatch.pl
Site	DriftSense self-monitor on local
Kind	local
Captured at	2026-07-12 00:48:56
Captured SHA	a53566efc691b4c13793a9302de362fb3dca2875d38088c15a6b03cc3b093fe2

Current state on disk

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

File present	yes
Size	22933 bytes
Current SHA	a53566efc691
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.