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/webstls.com/httpdocs/TEMPLATES/webstls_marketplaces.html
SiteWebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com)
Kindssh_agent
Captured at2026-07-01 22:27:01
Captured SHAe11d5355b6e121451aab4a8f5af4241b7c81edb7687a16bf65b2d9d1f8f4e179
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentyes
Size33979 bytes
Current SHAe11d5355b6e1
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.