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_stub.html
Site	PTMatrix (ptmatrix.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 12:35:09
Captured SHA	fced65320c5a3e56a4c80ca50e7a9ce172f96cfb1115d748a3a6a46ad7562a1f

Current state on disk

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

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