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/.htaccess
Site	PTMatrix (ptmatrix.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 12:33:51
Captured SHA	002a901f329376d6a8bd0b7b57419f4fcdc6979d079aed51c6df1b32cfba979a

Current state on disk

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

File present	yes
Size	2974 bytes
Current SHA	002a901f3293
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.