That makes sense on the repository side, but it seems like (even if this storage adapter is really just intending to be a stand-in for unit testing) we should make the semantics of storage consistent across all adapters, and in general it seems like storing/loading something is always saving/retrieving a copy of it at a particular point in time; edits to the authoritative, in-memory version shouldn't affect the saved version until `saveRegistry()` is called.