Restore
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/TEMPLATES/abforge_heatmaps.html
SiteABForge (abforge.3dshawn.com) on local
Kindlocal
Captured at2026-07-01 21:00:04
Captured SHAe85aacf6236fd898470aebe198dcf475b96f5e4721d491e1c77244657fa8c79c
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentyes
Size4982 bytes
Current SHAe85aacf6236f
Same as captured?yes -- no-op
Preflight compile-check ?
No compiler wired for this file type (unsupported). Restore is not gated.
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.
Cancel Logged to RESTORE_LOG regardless of outcome.