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_admin_user.html
Site	WebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com)
Kind	ssh_agent
Captured at	2026-07-11 18:31:17
Captured SHA	f680ea2791b5dc0d20f3177f307563f733b7fd9dfae44a9976ca6580ec0576e6

Current state on disk

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

File present	yes
Size	34176 bytes
Current SHA	f680ea2791b5
Same as captured?	yes -- no-op

See exactly what's different →

Confirm restore

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