@vheins/local-memory-mcp 0.10.11 → 0.11.0

package/dist/{chunk-5ODTDJZP.js → chunk-VXPBWGPZ.js}

@@ -81,8 +81,8 @@ function loadServerInstructions() {
 // src/mcp/capabilities.ts
 var __dirname2 = path2.dirname(fileURLToPath2(import.meta.url));
 var pkgVersion = "0.1.0";
-if ("0.10.11") {
-  pkgVersion = "0.10.11";
+if ("0.11.0") {
+  pkgVersion = "0.11.0";
 } else {
   let searchDir = __dirname2;
   for (let i = 0; i < 5; i++) {
@@ -3569,7 +3569,11 @@ var TOOL_DEFINITIONS = [
         task_code: { type: "string" },
         phase: { type: "string" },
         title: { type: "string", minLength: 3, maxLength: 100 },
-        description: { type: "string", minLength: 1 },
+        description: {
+          type: "string",
+          minLength: 1,
+          description: "Detailed description. MUST follow format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification"
+        },
         status: { type: "string", enum: ["backlog", "pending"], default: "backlog" },
         priority: {
           type: "number",
@@ -4096,7 +4100,10 @@ var TOOL_DEFINITIONS = [
           maxLength: 100,
           description: "Task objective (Required for single task)"
         },
-        description: { type: "string", description: "Detailed description (Required for single task)" },
+        description: {
+          type: "string",
+          description: "Detailed description. MUST follow format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification"
+        },
         status: {
           type: "string",
           enum: ["backlog", "pending"],
@@ -4126,7 +4133,10 @@ var TOOL_DEFINITIONS = [
               task_code: { type: "string" },
               phase: { type: "string" },
               title: { type: "string", minLength: 3, maxLength: 100 },
-              description: { type: "string" },
+              description: {
+                type: "string",
+                description: "Detailed description. MUST follow format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification"
+              },
               status: { type: "string", enum: ["backlog", "pending"], default: "backlog" },
               priority: {
                 type: "number",
@@ -4187,7 +4197,10 @@ var TOOL_DEFINITIONS = [
         task_code: { type: "string" },
         phase: { type: "string" },
         title: { type: "string", minLength: 3, maxLength: 100 },
-        description: { type: "string" },
+        description: {
+          type: "string",
+          description: "Detailed description. MUST follow format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification"
+        },
         status: {
           type: "string",
           enum: ["backlog", "pending", "in_progress", "completed", "canceled", "blocked"],

package/dist/dashboard/server.js

@@ -10,7 +10,7 @@ import {
   createFileSink,
   listResources,
   logger
-} from "../chunk-5ODTDJZP.js";
+} from "../chunk-VXPBWGPZ.js";
 
 // src/dashboard/server.ts
 import express from "express";

package/dist/mcp/server.js

@@ -57,7 +57,7 @@ import {
   toContextSlug,
   updateSessionFromInitialize,
   updateSessionRoots
-} from "../chunk-5ODTDJZP.js";
+} from "../chunk-VXPBWGPZ.js";
 
 // src/mcp/server.ts
 import readline from "readline";
@@ -1125,7 +1125,7 @@ function buildMissingTaskSchema(task) {
   });
   addRequiredStringField(properties, required, task, "description", {
     title: "Description",
-    description: "Detailed description of the task.",
+    description: "Detailed description. MUST follow format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification",
     minLength: 1
   });
   if (!task.status) {

package/dist/prompts/create-task.md

@@ -43,8 +43,8 @@ ONLY call MCP tools. No prose, no code, no plans outside MCP.
   - **Trigger**: Instruction/finding.
   - **Observation**: Technical reasoning.
   - **Goal**: Clear objective.
-  ### 2. Target Files & Implementation
-  - Combined scope/steps per path/layer.
+  ### 2. Step & Implementation
+  - Detailed execution steps per path/layer.
   ### 3. Acceptance & Verification
   - **Checklist**: `[ ]` criteria.
   - **Testing**: Scenarios.

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

@@ -40,8 +40,8 @@ ONLY call MCP tools. No prose, code, or external plans.
   - **Finding**: Gap trigger.
   - **Observation**: Reasoning.
   - **Goal**: Clear objective.
-  ### 2. Target Files & Implementation
-  - Combined scope/steps per path/layer.
+  ### 2. Step & Implementation
+  - Detailed execution steps per path/layer.
   ### 3. Acceptance & Verification
   - **Checklist**: `[ ]` criteria.
   - **Testing**: Scenarios.

package/dist/prompts/review-and-post-issue.md

@@ -42,7 +42,7 @@ No prose. No external plans.
   - **Finding**: Gap trigger.
   - **Observation**: Reasoning.
   - **Goal**: Clear objective.
-  ### 2. Target Files & Implementation
+  ### 2. Step & Implementation
   - Path/layer specific changes.
   ### 3. Acceptance & Verification
   - **Checklist**: `[ ]` criteria.

package/dist/prompts/session-planner.md

@@ -20,6 +20,6 @@ Steps:
 5. **Phase**: Group into `research`, `implementation`, and `validation`.
 6. **Hierarchy**: Use `parent_id` / `depends_on` for sequencing.
 7. **Priority Scale**: When creating tasks, use the exact MCP scale `1=Low`, `2=Normal`, `3=Medium`, `4=High`, `5=Critical`. Higher number means higher urgency.
-8. **Create**: Use `task-create` in current repo with stable `task_code`, tags, and acceptance criteria.
+8. **Create**: Use `task-create` in current repo with stable `task_code`, tags, and acceptance criteria following the format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification.
 
 Display final plan to user.

package/dist/prompts/task-memory-executor.md

@@ -35,7 +35,7 @@ agent: Task Executor
 ## 2. EXECUTION LOOP
 1. **Parallelism & Sub-Agents**: 
    - **MANDATORY**: Tasks MUST be delegated to sub-agents if the current agent has sub-agent capabilities.
-   - **Decomposition**: If a task is too broad, the agent is allowed to decompose it into multiple tasks (via `task-create`) and delegate them to sub-agents.
+   - **Decomposition**: If a task is too broad, the agent is allowed to decompose it into multiple tasks (via `task-create`) and delegate them to sub-agents. All created tasks MUST follow the format: 1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification.
    - **Spawn Limit**: The total number of parallel sub-agents MUST NOT exceed 2. Each sub-agent executes EXACTLY ONE task at a time.
    - **Fallback**: If the current agent CANNOT spawn sub-agents, it MUST execute tasks sequentially (exactly ONE concurrent task) until the queue is clear.
 2. **Hydrate**: Fetch full context via `task-detail` for the assigned task.
@@ -67,6 +67,33 @@ agent: Task Executor
      This ensures full traceability between code changes and project context.
    - **GitHub Issue Traceability**: If task metadata contains a GitHub Issue reference, the commit message MUST also include the issue hashtag in `#123` format.
    - **Issue Number Extraction**: Read the issue number from task metadata when available. If metadata only contains a GitHub Issue URL, extract the trailing issue number from that URL before committing.
+
+10A. **BLOCKER HANDLING (AUTOMATIC TASK CREATION)**:
+   - **Trigger**: When task status is updated to `blocked` with a comment explaining the blocker reason.
+   - **Blocker Classification**: Analyze the blocker comment to determine if it is **internal solvable** or **external**:
+     - **Internal Solvable** (auto-create task): Missing dependency, missing module/function, configuration/env setup, implementation gap, failing test, build error.
+     - **External** (skip auto-create): Awaiting user input/approval, API/service unavailability, manual external setup required.
+   - **Pattern Matching**: Use regex patterns to detect internal blockers in the comment:
+     - Missing patterns: `/(module|package|library|dependency|import)\s+(not\s+found|missing|undefined|not\s+installed)/i`
+     - Not implemented: `/(function|interface|class|method|endpoint)\s+not\s+(found|implemented|exists)/i`
+     - Configuration: `/(config|configuration|setup|env|environment)\s+(missing|not\s+set|invalid)/i`
+     - Test/build failure: `/(test|build|compile|type\s+check)\s+(failed|error)/i`
+   - **Auto-Create Task** (if internal solvable):
+     - Task Code: `${parent_task_code}-FIX-${unix_timestamp}`
+     - Title: `FIX: [${parent_task_title}] - Resolve: ${blocker_reason_extracted}`
+     - Description: Follow standard format (1. Context & Analysis, 2. Step & Implementation, 3. Acceptance & Verification)
+       - Context: Reference parent task code and explain the blocking factor
+       - Steps: Identify root cause and implement fix
+       - Verification: Confirm parent task can proceed
+     - Parent ID: Set to current blocked task ID
+     - Priority: `4` (HIGH)
+     - Phase: `blocker-resolution`
+     - Tags: `["blocker-fix", "auto-generated"]`
+     - Metadata: Include `triggered_by_task`, `blocker_reason`, `creation_timestamp`, and `agent_identity`
+   - **Update Parent Task**: Add comment linking to the new blocker-fix task: `"Blocker resolution task created: ${new_task_code}"`
+   - **Link Dependencies**: Set parent task's `depends_on` to the new blocker-fix task (parent waits for fix before retry)
+   - **Skip Creation** (if external): Log that blocker is external, keep task status as `blocked`, no automatic task created.
+
 11. **Repeat**: Claim next task from `task-list`.
 
 ## 3. BACKLOG MAINTENANCE
@@ -75,5 +102,94 @@ If active queue is empty:
 2. Move up to 20 highest-priority tasks to `pending` via `task-update`.
 3. Interpret priority using MCP ordering: `5=Critical`, `4=High`, `3=Medium`, `2=Normal`, `1=Low`.
 
-## 4. REPORT
+## 4. BLOCKER REFERENCE (Patterns & Detection)
+
+### Internal Solvable Blocker Patterns (Trigger Auto Task Creation)
+
+**Missing Dependencies/Modules**:
+- `module not found`, `missing dependency`, `import not installed`, `undefined function`, `no such file`
+- Example: "ImportError: Function 'validateToken' not found"
+
+**Not Implemented**:
+- `function/method not implemented`, `interface not exists`, `component undefined`
+- Example: "Function 'processPayment' not implemented - exists in type definitions but no implementation"
+
+**Configuration/Setup Issues**:
+- `.env missing`, `configuration not set`, `setup invalid`, `environment variable not found`
+- Example: "DATABASE_URL environment variable not set"
+
+**Test/Build Failures** (solvable):
+- `test failed`, `assertion failed`, `type error`, `build error`, `compilation failed`
+- Example: "Type error: Property 'user' does not exist on type 'Request'"
+
+**Implementation Gaps**:
+- `endpoint not implemented`, `API route missing`, `middleware not registered`
+- Example: "GET /api/users endpoint returns 404 - not implemented"
+
+### External Blocker Patterns (Skip Auto Task Creation)
+
+**Awaiting User/External Action**:
+- `awaiting user`, `requires manual`, `user must`, `external dependency`, `manual setup`
+- Example: "Awaiting user approval for database migration", "Requires manual infrastructure setup"
+
+**External Service Issues**:
+- `API not responding`, `service unavailable`, `server not ready`
+- Example: "Payment gateway API not responding - external service unavailable"
+
+**Manual Prerequisites**:
+- `install locally`, `run script manually`, `requires external tool`
+- Example: "Requires manual Docker setup - not part of this task"
+
+### Auto Task Creation Example Flow
+
+**Parent Task Blocked:**
+```
+Task Code: FEATURE-42
+Title: Add payment processing middleware
+Status: blocked
+Comment: "Function 'chargeCard' in services/payment.ts not implemented - exists in interface but implementation missing"
+```
+
+**Detection & Classification:**
+```
+Pattern detected: "Function .* not implemented" → INTERNAL SOLVABLE ✅
+Action: Create blocker-fix task
+```
+
+**Auto-Generated Task:**
+```
+Task Code: FEATURE-42-FIX-1714737908
+Title: FIX: [Add payment processing middleware] - Resolve: Function 'chargeCard' not implemented
+Parent ID: FEATURE-42
+Priority: 4 (HIGH)
+Phase: blocker-resolution
+Tags: ["blocker-fix", "auto-generated"]
+
+Description:
+1. Context & Analysis:
+   Parent task FEATURE-42 blocked due to: Function 'chargeCard' in services/payment.ts not implemented
+   The function exists in the interface but has no implementation body
+   Blocking factor: services/payment.ts - chargeCard function stub
+
+2. Step & Implementation:
+   - Review services/payment.ts chargeCard function signature
+   - Implement full payment processing logic (charges, refunds, error handling)
+   - Add proper error handling and validation
+   - Write unit tests for charge scenarios
+
+3. Acceptance & Verification:
+   - chargeCard function fully implemented
+   - Unit tests passing
+   - Function can be called from FEATURE-42 middleware
+   - FEATURE-42 parent task can proceed without blockers
+```
+
+**Execution Workflow:**
+1. Agent picks blocker-fix task first (independent, no dependencies)
+2. Implements `chargeCard` function
+3. Completes blocker-fix task
+4. Parent task FEATURE-42 becomes ready (fix completed)
+5. Agent proceeds with FEATURE-42 execution
+
+## 5. REPORT
 Provide progress summary.

package/package.json

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