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/MODS/ContactForge/Channels.pm
Site	ContactForge (crm.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 15:02:52
Captured SHA	6ed06756bf1b96f438f4dac46e73e070f5dec61313918403007e060d272628ae

Current state on disk

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

File present	yes
Size	338 bytes
Current SHA	6ed06756bf1b
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.