Accept a remote key for restore and verify, and document it (closes #124) #147

Open
clawbot wants to merge 1 commits from issue-124-restore-another-machine into next
1 Commits
Author SHA1 Message Date
sneak 68f4ccf5b9 Accept a remote key for restore and verify, and document it (closes #124)
check / check (pull_request) Failing after 1s
A host restoring after the original is gone has no local index and cannot
know a snapshot's human ID; `snapshot list` shows such snapshots only by
their remote key. Restore and verify now resolve an identifier to that
remote key: a human ID is hashed as before, and a remote key (or an
unambiguous leading part of it, as the table prints) is used directly,
resolved against the store's metadata listing. Deep verify reads the one
snapshot in the exported database rather than filtering by the human ID.

Adds an integration test that backs up with one index and hostname, then
lists, restores, and deep-verifies from the store with a fresh empty
index, a different hostname, and no age_recipients — comparing restored
bytes to the source. The empty index is what makes it fail if restore
ever needed the original one.

Adds a "Restoring on another machine" README section walking the flow end
to end, and drops the now-done roadmap item.

Model: claude-opus-4-8
2026-09-21 20:00:22 +00:00