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/crm.3dshawn.com/cgi-bin/test/test.cgi
Site	ContactForge (crm.3dshawn.com) on local
Kind	local
Captured at	2026-06-09 21:22:08
Captured SHA	3117bf3ce1f3f46446e41e3cc07e0140e69ee857511c2f0245bced9570734117

Current state on disk

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

File present	yes
Size	662 bytes
Current SHA	3117bf3ce1f3
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.