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/abforge.3dshawn.com/api_keys.cgi
Site	ABForge (abforge.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 16:00:59
Captured SHA	e826f3ff5153431e10677461af0e02bdba7b31a3097d7ddbd47477f7ee8f9b4c

Current state on disk

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

File present	yes
Size	2180 bytes
Current SHA	e826f3ff5153
Same as captured?	yes -- no-op

See exactly what's different →

Preflight compile-check ?

perl compiles cleanly — restore is safe to proceed.

Confirm restore

Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.