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/TEMPLATES/page_wrapper.html
Site	DriftSense self-monitor on local
Kind	local
Captured at	2026-07-12 01:04:51
Captured SHA	5b69348275539a86053804f7a2ff1ae7b3e43d7795956f98e517107e3fc1fafd

Current state on disk

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

File present	yes
Size	6871 bytes
Current SHA	5b6934827553
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.