v0.2.3

• Graph communities use a deterministic, dependency-free Leiden (modularity, resolution 1.0) instead of label propagation, which collapsed most of a real vault into one community. Every community is connected, ids are numbered by size then smallest member, and vault-graph.json and the report Overview record the partitioner, resolution and modularity. The vault graph, the workspace graph and skill mining share it.
• vmem graph build <vault> --workspace and vmem_graph_build with workspace: true build reports/workspace-graph.json: the vault graph plus the work layer (work docs, business-unit hubs, source: stubs and related, fm_ref, wiki_link, bu_member, source_ref and supersedes edges), a rule-for-rule port of build-graph.py --work-root. It writes only that file and one GRAPH event and returns the work counters and per-relation edge counts. bun scripts/workspace-parity.ts <vault> compares it against the Python reference, counts only.
• vmem skills mine <vault> and the MCP tool vmem_skills_mine rank new-skill candidates from agent-mem curated entries, agent-mem capture prompts, observations and summaries, and vault notes. They port the skill-mine dictionary matching, masking and scoring, cluster with vmem's deterministic graph communities, report counts by source and write nothing.

Install

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

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

Full changelog: v0.2.2...v0.2.3