Module init 

memstead init — bootstrap a filesystem mem in the current (or named) folder.

filesystem-mem is the single-mem, history-free, filesystem-backed product surface. After memstead init the folder contains:

• .memstead/config.json — workspace shape (schema pin, version; the mem name is path-derived). Pinned via memstead_base::filesystem::config.
• .memstead/cache/ — empty placeholder for any engine-managed cache data the workspace acquires later (e.g. resolved schema bytes).
• .memstead/memstead-io/ — empty directory the engine’s mem initialiser seeds. Nothing reads it: it held the cache the tier-3 archive resolver walked, and that resolver was removed on 2026-08-27 when registry attachments moved to the mount roster. Retiring the directory is a change to what init creates and is deliberately not folded in here.

No .gitignore is written — filesystem-mem does not assume a surrounding git repo, and writing one would surprise users who do track the workspace under git themselves.

Strict mode in non-empty folders: see plan trade-off “Adopt vs. strict for memstead init”. A non-empty target errors out cleanly so the user explicitly clears or moves files before initialising — never silently ingests unrelated .md files.

Structs

InitArgs

memstead init arguments.

Functions

run