v0.3.2

• Add library-only spec discovery, repository/worktree identity checks, typed id-based graphs and bounded directional slices (#91 T2). SpecIndex reuses the vault scan/metadata/hash/BM25 engine with a separate spec- cache per canonical worktree; vault cache names remain unchanged. Spec searches exclude shared-cache rows absent from the instance snapshot or replaced since its scan, and discovery errors name the relative file. Filesystem normalization/case aliases are accepted with root-identity and physical-containment checks, skipped listed paths have diagnostics, and error advice preserves the original cause and names .gitignore for discovery bounds. No CLI/MCP read surface or spec content write tools are added.

• Register local git roots separately with specs add|list|remove; removal previews and unregisters only. Spec root diagnostics distinguish a missing git executable, timeout, git refusal and non-root path, and support repository names containing backslashes. Spec sources default to write: none and pii: deny, share IDs and the atomic registry lock with vaults, and get root diagnostics in doctor. Config writes use format 2 only when specs is present; vault-only settings and output stay compatible. Spec graph/read/validation tools and spec content writes are not part of this increment (#91 T1).

• MCP argument errors name the first failing path and reason without echoing values; unknown tools have a separate diagnostic. vmem_create accepts top-level created and checks a real YYYY-MM-DD calendar date. Writer/log CLI errors name rejected options, writer arity errors show the expected form, and per-command --help/-h prints usage (#94).

• V05 refuses newly introduced Topics placement or content problems while retaining existing problems as warnings. frontmatter --set topics updates only the body Topics wiki-list items in the same atomic write, preserving fenced blocks, H3/prose and line endings; an unchanged topics value leaves the body unchanged. All create paths, including org promote and vmem_create with a custom body, now refuse a note whose Topics is not the final H2 or does not match its frontmatter topics. Existing vaults must run vmem tidy <vault> --all once after upgrading to the validating writer, previewing and then confirming its fingerprint; doctor reports pending migration counts and unparsable paths without writing, using only the planning pass, and reports thrown or returned planning failures as per-vault diagnostics (#92).

• Releases publish a GitHub release next to the npm package, with the validated tarball and manifest attached and the CHANGELOG section as notes (#89).

Install

npm i -g @staix/vault-mem@0.3.2

Published to npm with provenance through GitHub OIDC trusted publishing. The validated tarball (SHA-256 5d2fce549b675b5fa1cc5f73f34503b6e2bafb3badb51248e114ad8605cb8c15) and its manifest (tag, commit, SHA-256) from this run are attached.

Full changelog: v0.3.1...v0.3.2