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/abforge.3dshawn.com/_site_id_link_migration.sql
Site	ABForge (abforge.3dshawn.com) on local
Kind	local
Captured at	2026-07-06 01:16:36
Captured SHA	d145a8b3473a42bb17673c67537ca60b9e54ed9be28262a3e18169e044f30c33

Current state on disk

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

File present	no (new file)
Size	unknown
Current SHA
Same as captured?	no -- restore will change it

See exactly what's different →

Confirm restore

Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.