feat: perseus-vault connect -- one-command MCP client setup (PMB-inspired) (#333)

Add 'perseus-vault connect --client <name>' subcommand that auto-wires
an MCP client's config file, eliminating manual JSON/YAML/TOML editing
for first-time setup. Inspired by PMB's 'pmb connect' UX.

- Supports: claude-desktop, claude-code, hermes, cursor, windsurf,
  vscode, zed, codex.
- Merges into existing config (JSON objects, YAML mappings, TOML
  stanzas) without clobbering unrelated keys/servers already present.
- Writes a timestamped backup of the existing file before any write.
- --dry-run prints the would-be output without touching the filesystem.
- Codex TOML re-runs replace the existing [mcp_servers.mimir] stanza
  in place instead of duplicating it.
- Config path overridable via MIMIR_CONNECT_CONFIG (used by tests and
  non-standard installs).
- perseus-vault doctor now mentions 'connect' as the recommended setup
  path.
- 7 new unit tests (CLI parsing + real file writes/merges/idempotency
  across JSON/YAML/TOML backends); full suite 132 passed / 0 failed,
  stable across repeated runs (no test-order flakiness from
  set_current_dir / env var usage).
- Version bump 2.10.0 -> 2.11.0.

Author: tcconnally

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "perseus-vault"
-version = "2.10.0"
+version = "2.11.0"
 edition = "2021"
 description = "Persistent memory engine for AI agents — MCP JSON-RPC stdio server (formerly Mneme/Mimir)"
 repository = "https://github.com/Perseus-Computing-LLC/perseus-vault"

Cargo.toml

@@ -8,6 +8,9 @@ mimir serve --db ~/.mimir/data/mimir.db
 ```
 
 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
+manual JSON/YAML/TOML editing required).
 
 | Client | Status | Config file | Notes |
 |---|---|---|---|