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/etc/cron.d/drift_sense
SiteSSH-agent watch: /etc/cron.d on localhost-ssh-agent
Kindssh_agent
Captured at2026-07-12 23:14:05
Captured SHAd881083cab8f7e03293ca5488cf89f9af911b3185038a8783fa787012548d9e1
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentno (new file)
Sizeunknown
Current SHA
Same as captured?no -- restore will change it
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.