Both stores treat a missing file as an empty document, so a memory
directory that does not exist looked exactly like a memory with nothing
in it yet. archied logged "memory manager started" and ran with no
memory at all; the failure would have surfaced at the agent's first
write, as a tool error mid-conversation, long after startup said it was
fine.
Found live: a config copied from carina kept work_dir=/var/lib/archie
/work, a container path with no counterpart on the host.
New now establishes the directory and reports a path it cannot use, so
the existing error path exits at startup where an operator can see it.
Refs archie-core-rml