fix(onboarding): finish Mimir → Perseus Vault rename on the deploy surface (#429)

Client setup docs, MCP packaging manifests, framework integration docs,
transport docs, the clawhub skill, and awesome-mimir.md still used the old
`mimir` command and stale `~/.mimir/data/mimir.db` paths, so a fresh operator
copy-pasting any snippet got a config pointing at a binary the installer no
longer produces. All now use `perseus-vault` + the canonical
`~/.mimir/data/perseus-vault.db` default. manifest.json 2.13.0 -> 2.14.0;
awesome-mimir tool count 36 -> 55. The ~/.mimir/ dir is left for #427's shim.

(bootstrap.sh was already repaired on main by #425/#424; not re-touched.)

Co-authored-by: tcconnally <hermes@perseus.observer>

Author: tcconnally

CHANGELOG.md

@@ -25,6 +25,16 @@ All notable changes to Perseus Vault (formerly Mimir/Mneme) are documented here.
   success then fail to find the binary). It now builds/installs `perseus-vault`
   with `mimir`/`mneme` compat symlinks, defaults to `perseus-vault.db`, and
   uses the `serve` subcommand — matching `scripts/install.sh` (#424).
+- Onboarding/deploy surface completed the Mimir → Perseus Vault rename: client
+  setup docs (`docs/clients/README.md`, all 8 copy-paste snippets), MCP
+  packaging (`smithery.yaml`, `manifest.json` version `2.13.0` → `2.14.0`),
+  framework integration docs (langgraph/autogen + `docs/integration/*`),
+  transport docs, the clawhub skill, and `awesome-mimir.md` (tool count
+  `36` → `55`) now use the `perseus-vault` command and the canonical
+  `~/.mimir/data/perseus-vault.db` default path. Fresh operators copy-pasting
+  any client/integration snippet now get a working config that matches the
+  installed binary. The `~/.mimir/` support directory is intentionally
+  unchanged pending the migration-shim work in #427.
 
 ### Added
 - History retention mechanism (#398): entity_history can now be bounded via

awesome-mimir.md

@@ -53,9 +53,9 @@ Perseus Vault works with any MCP host. Configuration is one line:
 ```json
 {
   "mcpServers": {
-    "mimir": {
-      "command": "mimir",
-      "args": ["serve", "--db", "~/.mimir/data/mimir.db"]
+    "perseus-vault": {
+      "command": "perseus-vault",
+      "args": ["serve", "--db", "~/.mimir/data/perseus-vault.db"]
     }
   }
 }
@@ -71,7 +71,7 @@ Tested and confirmed working with:
 
 ## Tools & Plugins
 
-### Perseus Vault Itself (36 MCP Tools)
+### Perseus Vault Itself (55 MCP Tools)
 
 | Category | Tools |
 |---|---|
@@ -111,7 +111,7 @@ Why Perseus Vault stands out:
 
 | Feature | Perseus Vault | Mem0 | Letta | Zep |
 |---|---|---|---|---|
-| **MCP-Native** | ✅ 36 tools | ❌ | ❌ | ❌ |
+| **MCP-Native** | ✅ 55 tools | ❌ | ❌ | ❌ |
 | **Local-First** | ✅ Single binary | ❌ Cloud-dependent | ❌ Docker + Postgres | ❌ Docker + Postgres |
 | **Zero Dependencies** | ✅ SQLite bundled | ❌ Python + vector DB | ❌ Python + Postgres | ❌ Go + Postgres |
 | **Encryption at Rest** | ✅ AES-256-GCM | ❌ | ❌ | ❌ |

clawhub/skills/mimir/SKILL.md

@@ -85,17 +85,17 @@ Choose one:
 **Download binary (fastest):**
 ```bash
 # Linux x86_64
-curl -L https://github.com/Perseus-Computing-LLC/perseus-vault/releases/latest/download/mimir-linux-x86_64 -o mimir
-chmod +x mimir
-sudo mv mimir /usr/local/bin/
+curl -L https://github.com/Perseus-Computing-LLC/perseus-vault/releases/latest/download/perseus-vault-x86_64-unknown-linux-gnu -o perseus-vault
+chmod +x perseus-vault
+sudo mv perseus-vault /usr/local/bin/
 ```
 
 **Build from source (requires Rust):**
 ```bash
 git clone https://github.com/Perseus-Computing-LLC/perseus-vault.git
 cd perseus-vault
 cargo build --release
-sudo cp target/release/mimir /usr/local/bin/
+sudo cp target/release/perseus-vault /usr/local/bin/
 ```
 
 **Python client (optional, for scripts):**
@@ -111,7 +111,7 @@ Add to your OpenClaw MCP servers config:
 {
   "mcpServers": {
     "mimir": {
-      "command": "mimir",
+      "command": "perseus-vault",
       "args": ["--db", "~/.openclaw/mimir/mimir.db"],
       "env": {
         "MIMIR_ENCRYPTION_KEY": "${MIMIR_ENCRYPTION_KEY}"
@@ -126,7 +126,7 @@ For semantic search with embeddings, also set:
 {
   "mcpServers": {
     "mimir": {
-      "command": "mimir",
+      "command": "perseus-vault",
       "args": [
         "--db", "~/.openclaw/mimir/mimir.db",
         "--llm-endpoint", "http://localhost:11434"
@@ -156,10 +156,10 @@ Without an encryption key, Mimir stores data unencrypted (still local).
 mkdir -p ~/.openclaw/mimir
 
 # Start Mimir once to initialize
-mimir --db ~/.openclaw/mimir/mimir.db --health
+perseus-vault --db ~/.openclaw/mimir/mimir.db --health
 
 # Verify it's running
-mimir --db ~/.openclaw/mimir/mimir.db --stats
+perseus-vault --db ~/.openclaw/mimir/mimir.db --stats
 ```
 
 Then start a new OpenClaw session. Your agent now has access to all 23 Mimir memory tools.
@@ -168,7 +168,7 @@ Then start a new OpenClaw session. Your agent now has access to all 23 Mimir mem
 
 ```bash
 # Start the web dashboard on port 8789
-mimir --db ~/.openclaw/mimir/mimir.db --dashboard --port 8789
+perseus-vault --db ~/.openclaw/mimir/mimir.db --dashboard --port 8789
 # Open http://localhost:8789
 ```
 
@@ -203,13 +203,13 @@ Pair Mimir with these ClawHub skills for a complete memory stack:
 To run Mimir in CI or scheduled jobs:
 ```bash
 # Start Mimir in the background
-mimir --db /tmp/mimir_ci.db &
+perseus-vault --db /tmp/mimir_ci.db &
 
 # Run a coherence grooming pass nightly
-mimir --db ~/.openclaw/mimir/mimir.db --cohere
+perseus-vault --db ~/.openclaw/mimir/mimir.db --cohere
 
 # Export to vault for git backup
-mimir --db ~/.openclaw/mimir/mimir.db --vault-export ~/mimir-vault/
+perseus-vault --db ~/.openclaw/mimir/mimir.db --vault-export ~/mimir-vault/
 ```
 
 ## Links

docs/clients/README.md

@@ -1,23 +1,23 @@
-# Mimir — MCP Client Setup
+# Perseus Vault — MCP Client Setup
 
-Mimir is a standard **MCP stdio server**, so it works with every MCP-compatible
+Perseus Vault is a standard **MCP stdio server**, so it works with every MCP-compatible
 client. The command is always the same:
 
 ```
-mimir serve --db ~/.mimir/data/mimir.db
+perseus-vault serve
 ```
 
-Run `mimir doctor` to validate your install and print this matrix locally.
-Run `mimir connect --client <name>` to auto-wire a client's config file
-(merges a `mimir` MCP stanza into it, backing up the original first — no
+Run `perseus-vault doctor` to validate your install and print this matrix locally.
+Run `perseus-vault connect --client <name>` to auto-wire a client's config file
+(merges a `perseus-vault` MCP stanza into it, backing up the original first — no
 manual JSON/YAML/TOML editing required).
-Run `mimir prepare --task "<what you're about to do>"` for a pre-turn
+Run `perseus-vault prepare --task "<what you're about to do>"` for a pre-turn
 memory-prep block — combines `recall_when` (proactive trigger matches
 against the task text) and `context` (always-on + recent entities) into a
 single `<memory-prep>...</memory-prep>` block, zero LLM calls, ~10-50ms.
 Wire it into a Hermes/agent pre-turn hook so relevant memories are pushed
 into context before the model sees the prompt, instead of depending on the
-agent remembering to call `mimir_recall_when` itself. `--json` emits
+agent remembering to call `perseus_vault_recall_when` itself. `--json` emits
 structured output for programmatic hooks.
 
 | Client | Status | Config file | Notes |
@@ -36,49 +36,51 @@ structured output for programmatic hooks.
 
 ### Claude Desktop — `claude_desktop_config.json`
 ```json
-{ "mcpServers": { "mimir": { "command": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } }
+{ "mcpServers": { "perseus-vault": { "command": "perseus-vault", "args": ["serve"] } } }
 ```
 
 ### Claude Code — `.mcp.json` (project root)
 ```json
-{ "mcpServers": { "mimir": { "command": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } }
+{ "mcpServers": { "perseus-vault": { "command": "perseus-vault", "args": ["serve"] } } }
 ```
 
 ### Hermes — `~/.hermes/config.yaml`
 ```yaml
 mcp_servers:
-  mimir:
-    command: mimir
-    args: ["serve", "--db", "~/.mimir/data/mimir.db"]
+  perseus-vault:
+    command: perseus-vault
+    args: ["serve"]
 ```
 
 ### Cursor — `.cursor/mcp.json`
 ```json
-{ "mcpServers": { "mimir": { "command": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } }
+{ "mcpServers": { "perseus-vault": { "command": "perseus-vault", "args": ["serve"] } } }
 ```
 
 ### Windsurf — `mcp_config.json`
 ```json
-{ "mcpServers": { "mimir": { "command": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } }
+{ "mcpServers": { "perseus-vault": { "command": "perseus-vault", "args": ["serve"] } } }
 ```
 
 ### VS Code + Continue.dev — `config.json`
 ```json
-{ "mcpServers": { "mimir": { "command": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } }
+{ "mcpServers": { "perseus-vault": { "command": "perseus-vault", "args": ["serve"] } } }
 ```
 
 ### Zed — `settings.json`
 ```json
-{ "context_servers": { "mimir": { "command": { "path": "mimir", "args": ["serve", "--db", "~/.mimir/data/mimir.db"] } } } }
+{ "context_servers": { "perseus-vault": { "command": { "path": "perseus-vault", "args": ["serve"] } } } }
 ```
 
 ### Codex CLI — `~/.codex/config.toml`
 ```toml
-[mcp_servers.mimir]
-command = "mimir"
-args = ["serve", "--db", "~/.mimir/data/mimir.db"]
+[mcp_servers.perseus-vault]
+command = "perseus-vault"
+args = ["serve"]
 ```
 
-> Use an absolute `--db` path if your client runs Mimir from a different working
-> directory. Everything else is identical across clients because Mimir speaks
-> plain MCP stdio.
+> `perseus-vault serve` defaults its database to `~/.mimir/data/perseus-vault.db`
+> (with a legacy fallback chain). Pass an absolute `--db` path if your client
+> runs Perseus Vault from a different working directory or you want a specific
+> location. Everything else is identical across clients because Perseus Vault
+> speaks plain MCP stdio.

docs/integration/claude-code.md

@@ -18,8 +18,8 @@ cargo install --git https://github.com/Perseus-Computing-LLC/perseus-vault
 
 Verify:
 ```bash
-mimir --version
-# Expected: mimir 1.0.1
+perseus-vault --version
+# Expected: perseus-vault 2.14.0
 ```
 
 ### 2. Create a data directory
@@ -40,15 +40,15 @@ Create `.mcp.json` in your project root:
 ```json
 {
   "mcpServers": {
-    "mimir": {
-      "command": "mimir",
-      "args": ["--db", "/home/YOUR_USER/.mimir/data/mimir.db"]
+    "perseus-vault": {
+      "command": "perseus-vault",
+      "args": ["--db", "/home/YOUR_USER/.mimir/data/perseus-vault.db"]
     }
   }
 }
 ```
 
-Replace `/home/YOUR_USER/.mimir/data/mimir.db` with the absolute path to your
+Replace `/home/YOUR_USER/.mimir/data/perseus-vault.db` with the absolute path to your
 database. Do NOT use `~` — tilde expansion may not work in the MCP spawn context.
 
 **Global** (applies to all projects):
@@ -103,12 +103,12 @@ Claude Code will call `mimir_journal` to append a structured event.
 ### Perseus Vault tools don't appear
 
 1. **Absolute paths:** Ensure the `--db` argument uses a full absolute path.
-   `/home/user/.mimir/data/mimir.db` not `~/.mimir/data/mimir.db`.
+   `/home/user/.mimir/data/perseus-vault.db` not `~/.mimir/data/perseus-vault.db`.
 
-2. **Binary on PATH:** Run `which mimir`. If not found, install it or use
-   the full path in the `command` field: `/usr/local/bin/mimir`.
+2. **Binary on PATH:** Run `which perseus-vault`. If not found, install it or use
+   the full path in the `command` field: `/usr/local/bin/perseus-vault`.
 
-3. **Database writable:** The directory containing `mimir.db` must be writable
+3. **Database writable:** The directory containing `perseus-vault.db` must be writable
    by the user running Claude Code.
 
 4. **Restart Claude Code:** MCP servers are discovered at startup. After
@@ -118,20 +118,20 @@ Claude Code will call `mimir_journal` to append a structured event.
 
 ```bash
 chmod 755 ~/.mimir/data
-chmod 644 ~/.mimir/data/mimir.db
+chmod 644 ~/.mimir/data/perseus-vault.db
 ```
 
 ### Perseus Vault exits immediately
 
 Run Perseus Vault manually to check for startup errors:
 
 ```bash
-mimir --db ~/.mimir/data/mimir.db
+perseus-vault --db ~/.mimir/data/perseus-vault.db
 # Should hang waiting for stdin (this is correct — MCP stdio server)
 
 # If it exits with an error, check:
-# - SQLite is available (ldd $(which mimir) | grep sqlite)
-# - Database file is not corrupted (mimir --db /tmp/test.db to try a fresh DB)
+# - SQLite is available (ldd $(which perseus-vault) | grep sqlite)
+# - Database file is not corrupted (perseus-vault --db /tmp/test.db to try a fresh DB)
 ```
 
 ### Multiple Claude Code instances
@@ -140,7 +140,7 @@ SQLite WAL mode supports concurrent readers. If you see "database is locked",
 another process has an exclusive lock. Kill orphaned Perseus Vault processes:
 
 ```bash
-ps aux | grep '[m]imir'
+ps aux | grep '[p]erseus-vault'
 kill <PID>
 ```
 
@@ -151,9 +151,9 @@ kill <PID>
 ```json
 {
   "mcpServers": {
-    "mimir": {
-      "command": "mimir",
-      "args": ["--db", "/home/YOU/projects/my-project/.mimir/mimir.db"]
+    "perseus-vault": {
+      "command": "perseus-vault",
+      "args": ["--db", "/home/YOU/projects/my-project/.mimir/perseus-vault.db"]
     }
   }
 }
@@ -166,7 +166,7 @@ This keeps project memories isolated.
 Perseus Vault includes an optional web dashboard for browsing entities:
 
 ```bash
-mimir --db ~/.mimir/data/mimir.db --web --port 8767
+perseus-vault --db ~/.mimir/data/perseus-vault.db --web --port 8767
 ```
 
 Open `http://localhost:8767` in a browser. The dashboard shows entity lists,
@@ -177,18 +177,18 @@ search, graph visualization, and journal events.
 Generate a key and use it:
 
 ```bash
-mimir keygen --key-file ~/.mimir/secret.key
+perseus-vault keygen --key-file ~/.mimir/secret.key
 ```
 
 Then in `.mcp.json`:
 
 ```json
 {
   "mcpServers": {
-    "mimir": {
-      "command": "mimir",
+    "perseus-vault": {
+      "command": "perseus-vault",
       "args": [
-        "--db", "/home/YOU/.mimir/data/mimir.db",
+        "--db", "/home/YOU/.mimir/data/perseus-vault.db",
         "--encryption-key", "/home/YOU/.mimir/secret.key"
       ]
     }