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/admin_team.cgi
Site	ContactForge (crm.3dshawn.com) on local
Kind	local
Captured at	2026-07-11 18:31:46
Captured SHA	0dc5d0fa8ef9118fea95bdb3813501e17d4ecf2c15ab1db9fe02e9cb3ff575df

Current state on disk

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

File present	yes
Size	16835 bytes
Current SHA	0dc5d0fa8ef9
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.