fix(onboarding): finish Mimir → Perseus Vault rename on the deploy surface#429
Merged
Conversation
…urface 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.)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Time-to-value / deploy-readiness fix
Part of the enterprise deep-dive's time-to-value audit. bootstrap.sh (the build-from-source blocker) was already repaired on main by #425/#424; this PR finishes the rename across the rest of the operator-facing deploy surface, where a fresh operator copy-pasting any client/integration snippet still got the old
mimircommand and a stale~/.mimir/data/mimir.dbpath — a config pointing at a binary the installer no longer produces.Changed (12 files)
docs/clients/README.md— title + shared command + doctor/connect/prepare + all 8 copy-paste client snippets →perseus-vault(DB path omitted; binary self-defaults). Stalemimir_recall_when→perseus_vault_recall_when.smithery.yaml— command + default/example DB path →perseus-vault/perseus-vault.db.manifest.json— version2.13.0→2.14.0(matches Cargo.toml).integrations/langgraph,integrations/autogen,docs/integration/{claude-code,cursor,general-mcp}.md—mimircommand (incl.mimir keygen) →perseus-vault; canonical DB path. Per-integration DB filenames (crewaicrew.db) left intact; crewai/README unchanged.docs/transport.md— command + example DB filename + docker image → perseus-vault.clawhub/skills/mimir/SKILL.md— executable/command name + build/install steps → perseus-vault (dir/tool names/pip package left as-is).awesome-mimir.md— tool count36→55; config command/path.Scope guards
~/.mimir/support directory is intentionally unchanged — deferred to Complete on-disk rename: ~/mimir.db -> ~/perseus-vault.db, ~/.mimir/ -> ~/.perseus-vault/ (with migration shim) #427's migration-shim work.src/*.rstouched.mimir_*tool names, module/class identifiers, and intentional per-integration DB filenames preserved.Validation
manifest.json/server.json/glama.jsonparse OK;smithery.yamlparses OK.mimir-command ormimir.dbreferences remain in the changed onboarding files.🤖 Generated with Claude Code