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/TEMPLATES/tf_admin_seo.html
Site	PTMatrix (ptmatrix.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 12:34:50
Captured SHA	5463f5f52cc7d87cf069d620174a316fae1a4183313e9e0d1ae17d05727696ea

Current state on disk

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

File present	yes
Size	9146 bytes
Current SHA	5463f5f52cc7
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.