@projectpac/artifacts-memory

The artifact store's test double: history in memory, workspaces on disk. Not published, like every double here: it must not be installable as though it were the store.

The history is in memory because a test wants it gone with the process. The workspaces are real directories because that is what a model run writes into -- the loop takes a path and knows nothing about revisions -- so a double that kept files in a map would be testing something the node does not do.

It holds the same rules as the git-backed store, because it answers the same conformance suite: authorship proven by a signature the revision carries, one history per resource, a bundle verified before it is applied, and bounded workspaces.