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/admin.3dshawn.com/MODS/Login.pm
Site	Meta-Admin (admin.3dshawn.com) on local
Kind	local
Captured at	2026-06-22 16:19:48
Captured SHA	409b87da579de5d003b57cad6ff2408e0a7e760f74b8a4c3bedad23e0bf3b0ba

Current state on disk

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

File present	yes
Size	7894 bytes
Current SHA	409b87da579d
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.