@gethmy/mcp 2.5.0 → 2.5.2

package/README.md

@@ -5,7 +5,7 @@ Enables AI coding agents (Claude Code, OpenAI Codex, Cursor) to interact with yo
 
 ## Features
 
-- **67 MCP Tools** for full board control, knowledge graph, and workflow plans
+- **56 MCP Tools** for full board control, knowledge graph, and workflow plans
 - **Knowledge Graph Memory** - persistent memory with entity types, tiers, scopes, and typed relations
 - **Active Learning** - auto-extracts lessons, solutions, and error patterns from completed work sessions
 - **Context Assembly** - token-budget-aware memory injection into AI prompts
@@ -95,7 +95,7 @@ If you prefer to configure manually (e.g., in Claude.ai's UI):
 1. Get an API key from [Harmony](https://gethmy.com/user/keys)
 2. In Claude.ai, add a remote MCP server with URL `https://mcp.gethmy.com/mcp`
 3. Set the Authorization header to `Bearer hmy_your_key_here`
-4. All 67 Harmony tools become available in your conversation
+4. All 56 Harmony tools become available in your conversation
 
 **Session management** is automatic - sessions have a 1-hour TTL and are created/renewed transparently.
 
@@ -316,23 +316,6 @@ Store and retrieve persistent knowledge across sessions. Memories have types, ti
 - `harmony_resolve_links` - Batch-scan for `[[wiki-links]]` and auto-create relations
 - `harmony_sync` - Bidirectional sync between local markdown files (`~/.harmony/memory/`) and remote database (directions: `pull`, `push`, `full`)
 
-### Memory Lifecycle
-
-- `harmony_promote_memory` - Promote entity tier: `draft` → `episode` or `episode` → `reference`
-- `harmony_prune_draft` - Remove stale draft memories (dry-run mode by default)
-- `harmony_consolidate_memories` - Cluster similar draft/episode memories and merge into reference entities (dry-run by default)
-- `harmony_backfill_embeddings` - Generate vector embeddings for entities missing them
-- `harmony_backfill_relations` - Retroactively create semantic relations across existing entities
-- `harmony_cleanup_memories` - Bulk cleanup helper: flag stale drafts, dedupe boilerplate, trim low-value entries
-- `harmony_audit_memories` - Surface low-confidence or low-quality memories for human review
-- `harmony_purge_memories` - Hard-delete archived or flagged memories (dry-run by default)
-
-### Context Debugging
-
-- `harmony_get_context_manifest` - Debug what memories were loaded/excluded in a prompt assembly
-- `harmony_debug_context` - Explain why a specific memory was or wasn't included (relevance score breakdown)
-- `harmony_export_memory_graph` - Export knowledge graph as DOT format for Graphviz visualization
-
 ### GSD Workflow Plans
 
 Create and manage project plans with a phased workflow: **plan** → **execute** → **verify** → **done**.
@@ -526,7 +509,7 @@ Three test files pin the contract every MCP client depends on. They are mandator
 
 | File | What it pins |
 |---|---|
-| `src/__tests__/skills.test.ts` | `buildSkillFile` frontmatter, version-marker injection, agent-id substitution, parameterized over `SKILL_DEFINITIONS`. |
+| `src/__tests__/skills.test.ts` | `buildSkillFile` renderer contract: version-marker injection, body trimming, version-parse edge cases. Fed by `FetchedSkill` fixtures (DB-backed via `/v1/skills` post-#162 Phase 0). |
 | `src/__tests__/tool-dispatch.test.ts` | `TOOLS` registry shape, name uniqueness + `harmony_*` namespace, `inputSchema` validity, handler routing via `registerHandlers`, tool ↔ skill namespace boundary. |
 | `src/__tests__/mcp-integration.test.ts` | End-to-end `Client ↔ Server` round-trip over `InMemoryTransport` — `listTools`, `callTool`, `listResources`, `readResource`, plus error paths. |