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/UAParser.pm
Site	ContactForge (crm.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 15:02:58
Captured SHA	1d2e031c60d3e33254f67c64aed6262b9a8bd977037d2828233b2c73c8d56115

Current state on disk

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

File present	yes
Size	3100 bytes
Current SHA	1d2e031c60d3
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.