@vheins/local-memory-mcp 0.10.10 → 0.10.12

package/dist/dashboard/server.js

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

package/dist/mcp/server.js

@@ -57,7 +57,7 @@ import {
   toContextSlug,
   updateSessionFromInitialize,
   updateSessionRoots
-} from "../chunk-76IHLGKG.js";
+} from "../chunk-WWVIDZ5P.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

@@ -1,12 +1,19 @@
 ---
 name: task-memory-executor
 description: Sequentially execute pending tasks for current repository.
-arguments: []
+arguments:
+  - name: agent_identity
+    description: Optional runner identity (e.g., Codex-Jarvis, Codex-HulkBuster, Gemini-Ultron). If omitted, identity is inferred from the active CLI/IDE and a short session token is appended.
+    required: false
 agent: Task Executor
 ---
 
 ## 1. SYNC & FILTER
-1. **Identify**: Get repo name (git/context).
+1. **Identify**: Determine runner identity and repo context.
+   - Resolver priority: `agent_identity` argument -> auto session identity generated once per run.
+   - Auto identity format: `<runner>-<randomName>`.
+   - `<runner>` should come from the active CLI/IDE label (for example `vibe-coding-cli`, `vibe-coding-ide`, `Codex`, `Gemini`) and `<randomName>` is a short stable session token.
+   - Use this identity for all `task-claim`, `task-update`, and handoff writes.
 2. **List**: Call `task-list` ONCE for active tasks.
 3. **Dependency-aware selection** (in `task-list` order):
    - Process tasks in the order returned by `task-list`.
@@ -28,13 +35,13 @@ 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.
 3. **Readiness re-check**: Re-check blockers from hydrated detail (`depends_on`, `parent_id`) before claim. If still blocked, return to step 2 (execution loop) and pick the next ready task in list order.
-4. **Claim**: Use `task-claim` with `task_code` or `task_id` before implementation.
-5. **Start**: `task-update` status to `in_progress` (MUST transition: `pending` → `in_progress`). Add agent/role metadata.
+4. **Claim**: Use `task-claim` with `task_code` or `task_id` before implementation, and write the runner identity into claim metadata.
+5. **Start**: `task-update` status to `in_progress` (MUST transition: `pending` → `in_progress`). Add agent/role metadata and the same runner identity used by claims.
 6. **Research**: Call `memory-search` (Hybrid Search) and hydrate relevant results with `memory-detail`.
 7. **Standards (MANDATORY PER TASK)**: Call `standard-search` for every task inside the execution loop before any code edit, test edit, refactor, migration, or implementation decision, using the task intent, affected files, inferred language, stack, and repo as filters. This is required even for small tasks, decomposed tasks, and sub-agent assignments. Apply only relevant standards, hydrate details when needed, and if no relevant standards are returned, continue and state that no applicable standards were found.
 8. **Execute**:
@@ -50,7 +57,7 @@ agent: Task Executor
    - **Cleanup**: Completing/canceling a task automatically releases active claims and expires linked pending handoffs.
    - **Memory**: Store insights as `code_fact`/`pattern` via `memory-store`.
    - **Standards**: Store durable implementation rules via `standard-store`, not generic memory.
-   - **Handoff**: If work remains or ownership changes, create `handoff-create` with concise summary and structured context containing next steps/blockers/remaining work. Do not create handoffs for completed-work summaries.
+   - **Handoff**: If work remains or ownership changes, create `handoff-create` with concise summary and structured context containing next steps/blockers/remaining work. Do not create handoffs for completed-work summaries. Include runner identity in handoff metadata/context.
    - **Retrospective**: Invoke `learning-retrospective`.
    - **Commit**: Atomic git commit. The commit message MUST follow this format: `type(scope): [task-code] your commit message`, followed by a detailed description:
      ```

package/package.json

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