Expand description
memstead install — two accepted input shapes:
memstead install <path/to/file.mem>— local-file install.memstead install <scope>/<name>— registry install. Downloads the archive from<registry>/api/mem/<scope>/<name>.meminto a tempfile, then funnels through the same cache helper the local path uses. No authentication required — registry downloads are public.
Both shapes:
- Validate and copy (or re-validate) the archive into the global
mem cache (
<data_dir>/memstead/mems/<name>-<key>.mem). - Register the archive as a workspace-level read-only mount
in the engine-managed mount state (
.memstead/state/mounts.json), carryingcapability: read_onlyand the content-addressed cache path as itsArchivestorage reference. No writable mem’s config is touched — a read-mem attaches to the workspace, not to a host mem.memstead uninstall <name>is the symmetric removal.
Structs§
- Args
- Install a sealed mem archive: validate + copy into the global mem
cache, then register it as a workspace-level read-only mount. The
archive’s internal name is its sole identity — cross-mem references
and shadow checks use it. Archives with non-slug-form body
wiki-links refuse with
INVALID_WIKI_LINK_TARGET— convert via search-and-replace before installing.