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/ptmatrix.3dshawn.com/accept_invite.cgi
Site	PTMatrix (ptmatrix.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 12:33:52
Captured SHA	f5585dc98aaa47a10ed8b5623bd867b5b4b5f0a3fe22ad9ab2c5b69fbb1d0e80

Current state on disk

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

File present	yes
Size	138 bytes
Current SHA	f5585dc98aaa
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.