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/admin_promotion_action.cgi
SiteWebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com)
Kindssh_agent
Captured at2026-07-01 22:26:18
Captured SHA5def38a3eed081108045829a9e823bddc732e03f5704186a809646fc4391516c
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentyes
Size148 bytes
Current SHA5def38a3eed0
Same as captured?yes -- no-op
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.
Cancel Logged to RESTORE_LOG regardless of outcome.