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/repricer.3dshawn.com/MODS/RePricer/ImportAdapters.pm
Site	RePricer (repricer.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 21:47:11
Captured SHA	5c6cfc8cd655815c3553f8d2005c77600fe9cf378e178e8e24e2277f6396fb05

Current state on disk

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

File present	yes
Size	58163 bytes
Current SHA	5c6cfc8cd655
Same as captured?	yes -- no-op

See exactly what's different →

Preflight compile-check ?

perl compile FAILED — restore is blocked unless you tick "force override" below.

Invalid version format (non-numeric data) at  line 1128, near "package MODS::RePricer::ImportAdapters::Best "
BEGIN not safe after errors--compilation aborted at  line 1129.

Confirm restore

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