replen 1.0.19 → 1.0.20

package/dist/commands.js

@@ -577,6 +577,6 @@ export async function runAtlas(argv) {
         console.log(JSON.stringify({ dir, count: data.files.length }));
         return;
     }
-    console.log(`Atlas written: ${data.files.length} notes → ${dir}`);
-    console.log(`Open ${dir} in Obsidian (or any markdown editor) to explore the graph view of your projects, capabilities, and decisions.`);
+    console.log(`Atlas: ${data.files.length} tiles written → ${dir}`);
+    console.log(`Open ${dir} in Obsidian (or any markdown editor) — the tiles stitch into the graph view of your projects, capabilities, and decisions.`);
 }

package/extras/skills/replen/SKILL.md

@@ -344,7 +344,7 @@ The user hasn't set up filter-mode B's tag list. Mention it once: "Heads
 up — you'd get sharper matches if you set project tags at /settings.
 Continuing with unfiltered for now."
 
-## The Atlas vault — local memory for any agent
+## Atlas tiles — local memory for any agent
 
 Replen keeps an agent-readable markdown vault at `~/.replen/atlas/` — the
 user's whole portfolio as linked notes: every project and what it does,
@@ -356,8 +356,8 @@ The MCP server refreshes it in the background (at most twice a day);
 Use it whenever you need CROSS-PROJECT context: "what else does this user
 build?", "have we solved X in another repo?", "what did we decide about
 Y last quarter?". Start at `MAP.md`, or call `replen_recall` for a direct
-query. Reading the vault beats re-deriving the portfolio from scratch —
-it's the memory layer, and it's already on disk.
+query. Reading the tiles beats re-deriving the portfolio from scratch —
+they're the memory layer, and they're already on disk.
 
 ## When NOT to run this skill
 

package/extras/skills/replen-onboard/SKILL.md

@@ -89,7 +89,7 @@ grounding source (faster AND richer than a cold code-read):
 
 If you ground from one of these, START the report (2c) with one line:
 `Grounding source: Graphify vault at <path>` (or `Obsidian vault…` / `ADRs…`)
-— it renders into the user's Atlas vault, linking the two tools. Then skim the
+— it renders into the user's Atlas tiles, linking the two tools. Then skim the
 code only to VERIFY (the vault may be stale); don't re-derive what it already
 holds. Privacy is unchanged: only capabilities/descriptors/paths/tags leave
 the machine, exactly as with a code-read — never vault content or code.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replen",
-  "version": "1.0.19",
+  "version": "1.0.20",
   "description": "Make your AI coding tools smarter. One command, no API keys, free. Replen watches what your projects actually do and surfaces a few things worth bringing in each month. Use one as is, port a piece of another, cherry pick an idea, or build it clean room. The match happens inside your AI tool's session. A few actionable matches a month, by design.",
   "type": "module",
   "bin": {