@vheins/local-memory-mcp 0.5.11 → 0.5.13

package/dist/mcp/prompts/definitions/create-task.md

@@ -29,6 +29,7 @@ You are **STRICTLY FORBIDDEN** from performing any of the following actions:
 **Allowed Actions:**
 * Read code and analyze context
 * Create tasks via `@vheins/local-memory-mcp tools task-create`
+* Record decisions via `@vheins/local-memory-mcp tools memory-store`
 * List tasks via `@vheins/local-memory-mcp tools task-list`
 * Search memory via `@vheins/local-memory-mcp tools memory-search`
 
@@ -38,6 +39,7 @@ You are **STRICTLY FORBIDDEN** from performing any of the following actions:
 
 Your output MUST ONLY consist of calls to:
 * `@vheins/local-memory-mcp tools task-create`
+* `@vheins/local-memory-mcp tools memory-store`
 * `@vheins/local-memory-mcp tools task-list`
 * `@vheins/local-memory-mcp tools memory-search`
 
@@ -100,14 +102,20 @@ The `description` field MUST follow this structure EXACTLY:
 
 ---
 
-### 4. MULTI-TASK HANDLING
+### 4. MEMORY STORAGE (CONDITIONAL)
+If the instruction or prompt involves a decision, new feature, or architectural change, you MUST log it as a memory using `@vheins/local-memory-mcp tools memory-store` with `type: decision`. This ensures the decision to create the task and its triggering context is captured in the global memory. 
+**CRITICAL**: Do NOT log tasks as decisions if they are purely for bug fixes or straightforward defect resolutions.
+
+---
+
+### 5. MULTI-TASK HANDLING
 If a directive is complex:
 1. Create a parent task.
 2. Create child tasks using `parent_id` and `depends_on`.
 
 ---
 
-### 5. FINAL SELF-CHECK (MANDATORY)
+### 6. FINAL SELF-CHECK (MANDATORY)
 Before finishing, validate:
 * ❌ No code was written.
 * ❌ No execution was performed.

package/dist/mcp/prompts/definitions/review-and-audit.md

@@ -38,6 +38,7 @@ You are **STRICTLY FORBIDDEN** from performing any of the following actions:
 * Read code and analyze context
 * Use `chrome-dev-tools` MCP to inspect browser UX
 * Create tasks via `@vheins/local-memory-mcp tools task-create`
+* Record decisions via `@vheins/local-memory-mcp tools memory-store`
 * List tasks via `@vheins/local-memory-mcp tools task-list`
 * Search memory via `@vheins/local-memory-mcp tools memory-search`
 
@@ -46,6 +47,7 @@ You are **STRICTLY FORBIDDEN** from performing any of the following actions:
 ### ✅ ALLOWED OUTPUT (STRICT)
 If gaps are found, your output MUST ONLY consist of calls to:
 * `@vheins/local-memory-mcp tools task-create`
+* `@vheins/local-memory-mcp tools memory-store`
 * `@vheins/local-memory-mcp tools task-list`
 * `@vheins/local-memory-mcp tools memory-search`
 
@@ -105,14 +107,20 @@ The `description` field MUST follow this structure EXACTLY:
 
 ---
 
-### 6. MULTI-TASK HANDLING
+### 6. MEMORY STORAGE (CONDITIONAL)
+If the finding or gap involves a decision, new feature, or architectural change, you MUST log it as a memory using `@vheins/local-memory-mcp tools memory-store` with `type: decision`. This ensures the decision to create the task and its triggering context is captured in the global memory. 
+**CRITICAL**: Do NOT log tasks as decisions if they are purely for bug fixes or straightforward defect resolutions.
+
+---
+
+### 7. MULTI-TASK HANDLING
 If gaps are complex:
 1. Create a parent task.
 2. Create child tasks using `parent_id` and `depends_on`.
 
 ---
 
-### 7. FINAL SELF-CHECK (MANDATORY)
+### 8. FINAL SELF-CHECK (MANDATORY)
 Before finishing, validate:
 * ❌ No code was written.
 * ❌ No execution was performed.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vheins/local-memory-mcp",
-	"version": "0.5.11",
+	"version": "0.5.13",
 	"description": "MCP Local Memory Service for coding copilot agents",
 	"mcpName": "io.github.vheins/local-memory-mcp",
 	"type": "module",