v0.5.0 — BREAKING: rename binary to tencentdb-mem

Breaking change. CLI binary renamed claude-mem → tencentdb-mem to eliminate Anthropic brand collision and reflect honest fork attribution to TencentDB (the upstream project).

What changed

• Binary: claude-mem → tencentdb-mem (all commands)
• All hook commands, wrappers, scheduler, MCP registration updated
• All docs reference new binary

Unchanged (intentional)

• npm package @vkirill/tencentdb-memory-claude-code
• GitHub repo TencentDB-Memory-Claude-Code
• MCP server name tencentdb-memory + tool prefix mcp__tencentdb-memory__* (already renamed in v0.4.2)
• ~/.claude/claude-mem.env (env file — kept stable so keys aren't lost)
• ~/.claude/claude-mem-projects.txt (allowlist filename — stable)
• ~/.claude/hooks/claude-mem/ (hooks dir, internal path)

Upgrade (mandatory)

# 1. Remove old install (npm doesn't auto-clean bin on rename)
npm uninstall -g @vkirill/tencentdb-memory-claude-code

# 2. Install v0.5.0
npm i -g github:VKirill/TencentDB-Memory-Claude-Code#v0.5.0

# 3. Re-run install.sh — AUTO-MIGRATES old claude-mem references in hooks + MCP config
bash $(npm root -g)/@vkirill/tencentdb-memory-claude-code/claude-code-integration/install.sh

# 4. Restart PM2 + Claude Code
pm2 restart claude-mem-scheduler
# (kill + relaunch Claude Code)

# 5. Verify
tencentdb-mem --version    # → 0.5.0
which claude-mem            # → (not found — expected)

Verified: 91/91 tests, fresh install + migration both pass, MCP server still reports tencentdb-memory.