What I saved (5 memory files)

 - user-rodolico — who you are, and that this repo is SVN, not git (so "commit" = svn commit).
 - sneakernet-overview — the non-obvious operational model: one config/both roles via hostname, distinct source/target parents, FreeBSD GPT-label mount, openssl + .IV sidecar, the source→target serial.txt ordering rule.
 - sneakernet-recent-work — the v1.6.0–1.9.0 features (verification, status carry-over + backups, full-overwrite, xz compression, the checkSneakernetFile fix, TESTING.md) and the one open item: full-mode verification on an initial full send, unconfirmed on real ZFS.
 - sneakernet-change-conventions — bump version + CHANGELOG + datastructure + docs together; gate destructive ops behind a default-off flag and only act on the specific recognized condition; missing config fails safe toward more verification.
 - zfs-utils-testing — no zfs on this dev box; the extract-and-stub harness for unit-testing script subs.

These live in this project's memory dir and the index loads automatically when you start a session here.

## Prompt to recall
Start a session in this project directory and use something like:

"Catch me up on the sneakernet / zfs_utils project — recall what you know about it: the deployment model, the v1.6.0–1.9.0 work, our change conventions, and any open items."

The MEMORY.md index loads on its own, and that prompt pulls in the detailed files. If you just want the loose end: "What was the open verification item we left for the ZFS test box?" will surface the full-mode-on-initial-full question from sneakernet-recent-work.