@vheins/local-memory-mcp 0.10.2 → 0.10.3

package/dist/{chunk-FFPZ7JBM.js → chunk-HXADESDJ.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.2") {
-  pkgVersion = "0.10.2";
+if ("0.10.3") {
+  pkgVersion = "0.10.3";
 } else {
   let searchDir = __dirname2;
   for (let i = 0; i < 5; i++) {

package/dist/dashboard/server.js

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

package/dist/mcp/server.js

@@ -57,7 +57,7 @@ import {
   toContextSlug,
   updateSessionFromInitialize,
   updateSessionRoots
-} from "../chunk-FFPZ7JBM.js";
+} from "../chunk-HXADESDJ.js";
 
 // src/mcp/server.ts
 import readline from "readline";

package/dist/prompts/architecture-design.md

@@ -3,17 +3,21 @@ name: architecture-design
 description: Plan system architecture, component layout, and data flow
 arguments:
   - name: tech_stack
-    description: Technology stack
-    required: true
+    description: Technology stack. Optional — auto-detected from repo package files, language, and active task tags if omitted.
+    required: false
   - name: requirements
-    description: Key requirements
-    required: true
+    description: Key requirements. Optional — inferred from active task description, pending handoff, or recent conversation if omitted.
+    required: false
 agent: System Architect
 ---
-Design system architecture for repository.
+## 0. CONTEXT RESOLUTION
+- **tech_stack**: If provided, use directly. If omitted — detect from package.json, pyproject.toml, Gemfile, or repo file extensions.
+- **requirements**: If provided, use directly. If omitted — extract from active `in_progress` task description, pending handoff context, or recent conversation.
 
-Stack: {{tech_stack}}
-Requirements: {{requirements}}
+Design system architecture for the active repository.
+
+Stack: (resolved above)
+Requirements: (resolved above)
 
 Output:
 1. **Component Diagram**: Blocks & responsibilities.

package/dist/prompts/create-task.md

@@ -3,8 +3,8 @@ name: create-task
 description: Create structured, atomic tasks in Local Memory MCP.
 arguments:
   - name: instruction
-    description: Directive to analyze and break into tasks.
-    required: true
+    description: Directive to analyze and break into tasks. Optional — derived from active task, pending handoff, or recent conversation if omitted.
+    required: false
 agent: Task Planner
 ---
 

package/dist/prompts/csl-from-docs.md

@@ -3,14 +3,15 @@ name: csl-from-docs
 description: Create atomic CSL coding standards entries from a local file or directory path.
 arguments:
   - name: path
-    description: Local path (file or directory) containing documentation or standards.
-    required: true
+    description: Local path (file or directory) containing documentation or standards. Optional — defaults to docs/, README, or prompts definitions directory of the active repo if omitted.
+    required: false
 agent: Documentation Processor
 ---
-Fetch and convert local documentation from the provided path into atomic CSL (Coding Standards Library) entries for the coding_standards entity.
+## 0. CONTEXT RESOLUTION
+- **path**: If provided, use directly. If omitted — default to `docs/`, `README.md`, or `src/mcp/prompts/definitions/` in the active repo root.
+- **current_repo**: Auto-detect from git remote or active workspace context.
 
-Path: {{path}}
-Current repo: {{current_repo}}
+Fetch and convert local documentation from the resolved path into atomic CSL (Coding Standards Library) entries.
 
 Goal:
 - Analyze the provided path.

package/dist/prompts/csl-scrapper.md

@@ -3,14 +3,15 @@ name: csl-scrapper
 description: Scrape trusted documentation from a URL into atomic CSL coding standards entries.
 arguments:
   - name: source_url
-    description: Canonical URL for the documentation source to scrape.
-    required: true
+    description: Canonical URL for the documentation source to scrape. Optional — if omitted, use the most recently referenced URL from conversation context.
+    required: false
 agent: Documentation Scraper
 ---
-Fetch and convert trusted documentation from the provided URL into atomic CSL (Coding Standards Library) entries for the coding_standards entity.
+## 0. CONTEXT RESOLUTION
+- **source_url**: Use `{{source_url}}` if provided. If omitted — extract from the most recently mentioned URL in conversation context or active task description.
+- **current_repo**: Auto-detect from git remote or active workspace context.
 
-Source URL: {{source_url}}
-Current repo: {{current_repo}}
+Fetch and convert trusted documentation from the resolved URL into atomic CSL (Coding Standards Library) entries.
 
 Goal:
 - Use the web_fetch tool (if available) to retrieve the content of the provided Source URL.

package/dist/prompts/export-task-to-github.md

@@ -2,34 +2,32 @@
 name: export-task-to-github
 description: Export local tasks to GitHub Issues
 arguments:
-  - name: owner
-    description: GitHub repo owner
-    required: true
-  - name: repo
-    description: GitHub repo name
-    required: true
   - name: task_id
-    description: Local task ID
-    required: true
+    description: Local task ID. Optional — if omitted, all tasks in the active repo are exported.
+    required: false
 agent: Integration Architect
 ---
 
-## 1. RETRIEVE
-1.  **Fetch**: Call `task-detail` for `task_id`.
-2.  **Verify**: Ensure title/description exist. Use `memory-search` for gaps.
+## 1. IDENTIFY ACTIVE PROJECT
+1.  **Detect**: Get repo name and owner from git remote (e.g. `git remote get-url origin`) or active workspace context. Parse `owner` and `repo` from the remote URL automatically.
+2.  **Verify**: Confirm the detected `owner`/`repo` before proceeding.
 
-## 2. SYNC CHECK
-1.  **Search**: Use `search_issues` for `task_code`.
+## 2. RETRIEVE
+1.  **Scope**: If `task_id` provided — fetch that single task via `task-detail`. If omitted — call `task-list` (status: `pending,in_progress,completed`) to get all tasks in the active repo, then process each.
+2.  **Verify**: Ensure title/description exist per task. Use `memory-search` for gaps.
+
+## 3. SYNC CHECK
+1.  **Search**: Use `search_issues` for `task_code` scoped to detected `owner`/`repo`.
 2.  **De-duplicate**: If issue exists, update local task `metadata` with URL. DO NOT re-create.
 
-## 3. CREATE ISSUE
+## 4. CREATE ISSUE
 If new:
--   **Write**: Use `issue_write` (method: 'create').
+-   **Write**: Use `issue_write` (method: 'create') with detected `owner`/`repo`.
 -   **Content**: Match local title/body exactly.
 -   **Traceability**: Append `task_code` and `task_id` to body.
 -   **Comments**: Post local comments via `add_issue_comment`.
 
-## 4. LINK
+## 5. LINK
 -   **Update**: Call `task-update`.
 -   **Metadata**: Add GitHub URL.
 -   **Comment**: "Exported to GitHub Issue #X".

package/dist/prompts/fix-suggestion.md

@@ -3,21 +3,24 @@ name: fix-suggestion
 description: Targeted fix with before/after code and test case.
 arguments:
   - name: tech_stack
-    description: Target tech stack.
-    required: true
+    description: Target tech stack. Optional — inferred from repo/context if omitted.
+    required: false
   - name: bug_description
-    description: Bug behavior.
-    required: true
+    description: Bug behavior. Optional — inferred from active conversation or task context if omitted.
+    required: false
   - name: root_cause
-    description: Identified root cause.
-    required: true
+    description: Identified root cause. Optional — inferred from recent error/log context if omitted.
+    required: false
 agent: Debugging Expert
 ---
-Provide precise, minimal fix for confirmed bug.
 
-Stack: {{tech_stack}}
-Bug: {{bug_description}}
-Cause: {{root_cause}}
+## 0. CONTEXT RESOLUTION
+Resolve missing arguments from available context before proceeding:
+- **tech_stack**: Detect from repo language, package files, or active task tags. Fallback: ask agent to infer from open files.
+- **bug_description**: Extract from active task description, recent conversation, or error logs. Fallback: describe observable broken behavior.
+- **root_cause**: Extract from recent analysis, error traces, or `memory-search` results. Fallback: state "unknown — investigation required".
+
+Provide precise, minimal fix for confirmed bug.
 
 Output:
 1. **Explanation**: Why it happens & how fix works.

package/dist/prompts/learning-retrospective.md

@@ -3,11 +3,15 @@ name: learning-retrospective
 description: Harvest knowledge from completed work.
 arguments:
   - name: task_id
-    description: ID of completed task.
+    description: ID or code of completed task. Optional — defaults to most recently completed task in the active repo.
     required: false
 agent: Knowledge Harvester
 ---
-Extract durable knowledge from task {{task_id}} for repository.
+## 0. CONTEXT RESOLUTION
+1. **Repo**: Auto-detect from git remote or active workspace context. All MCP calls MUST be scoped to this repo.
+2. **Task**: If `task_id` provided — use it directly. If omitted — call `task-list` (status: `completed`, limit: 1, ordered by updated_at desc) to get the most recently completed task.
+
+Extract durable knowledge from the resolved task for the active repository.
 
 Identify and `memory-store`:
 1. **Mistakes**: Hard-to-find bugs or environment quirks.

package/dist/prompts/memory-guided-review.md

@@ -3,11 +3,14 @@ name: memory-guided-review
 description: Review code for compliance with stored decisions.
 arguments:
   - name: file_path
-    description: File to review.
-    required: true
+    description: File to review. Optional — if omitted, review the currently open/active file in the workspace, or all recently modified files.
+    required: false
 agent: Code Auditor
 ---
-Audit {{file_path}} against stored project knowledge.
+## 0. CONTEXT RESOLUTION
+- **file_path**: If provided, use it. If omitted — use the currently active/open file from workspace context, or list recently modified files via git and process them.
+
+Audit the resolved file(s) against stored project knowledge.
 
 Steps:
 1. **Search Memory**: Call `memory-search` using `current_file_path='{{file_path}}'`.

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

@@ -3,16 +3,20 @@ name: review-and-audit
 description: Audit documentation against implementation; generate local tasks for gaps.
 arguments:
   - name: target
-    description: Module, feature, or component to audit.
+    description: Module, feature, or component to audit. Optional — if omitted, audits all available documentation against the full implementation.
     required: false
 agent: Quality Auditor
 ---
 
+## 0. CONTEXT RESOLUTION
+- **Target**: If `target` provided — scope audit to that module/feature/component. If omitted — **fallback**: audit ALL existing documentation (README, docs/, prompts, schemas) against the full codebase implementation. Enumerate each doc file and compare with corresponding source.
+- **Repo**: Auto-detect from git remote or active workspace context.
+
 ## 1. ANALYSIS
-1. **Sequential Discovery**: Explore docs and code sequentially. NO parallel sub-agents.
-2. **UX Audit**: Use `chrome-dev-tools` for visual, navigation, and responsiveness checks.
+1. **Discovery**: Explore docs and code. Coding sub-agents MAY be used for parallel file reading if the agent supports sub-agents. `chrome-devtools-mcp` MCP tools (direct tool calls) are **ALLOWED**. **FORBIDDEN**: spawning a `browser_subagent` — do NOT invoke the `browser_subagent` tool here. Distinction: MCP tool call = allowed; spawned browser agent process = forbidden.
+2. **UX Audit**: If target involves UI and the audit explicitly requires visual inspection, note it as a separate task — do NOT block the audit on it.
 3. **Reference Audit**: Check current tool/prompt/resource definitions through code or the dashboard Reference flow.
-4. **Compare**: Match docs + code findings against live UI to find gaps/misalignments.
+4. **Compare**: Match docs + code findings to find gaps/misalignments.
 
 ## 🚫 FORBIDDEN: NON-EXECUTION
 DO NOT edit/create/delete files, run commands, or implement code.

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

@@ -3,21 +3,25 @@ name: review-and-post-issue
 description: Audit documentation against implementation; generate GitHub issues for gaps.
 arguments:
   - name: owner
-    description: GitHub repo owner.
-    required: true
+    description: GitHub repo owner. Optional — auto-detected from git remote if omitted.
+    required: false
   - name: repo
-    description: GitHub repo name.
-    required: true
+    description: GitHub repo name. Optional — auto-detected from git remote if omitted.
+    required: false
   - name: target
-    description: Module, feature, or component to audit.
+    description: Module, feature, or component to audit. Optional — if omitted, audits all documentation against the full implementation.
     required: false
 agent: Quality Auditor
 ---
 
+## 0. CONTEXT RESOLUTION
+1. **Owner/Repo**: Auto-detect from `git remote get-url origin` or active workspace context. Parse `owner` and `repo` from the remote URL. Verify before proceeding.
+2. **Target**: If `target` provided — scope to that module/feature. If omitted — **fallback**: audit ALL existing documentation against the full codebase.
+
 ## 1. ANALYSIS
-1. **Sequential Discovery**: Explore docs and code sequentially. NO parallel sub-agents.
-2. **UX Audit**: If applicable, use `chrome-dev-tools` for visual, navigation, and responsiveness checks.
-3. **Compare**: Match findings against live UI to find gaps/misalignments.
+1. **Discovery**: Explore docs and code. Coding sub-agents MAY be used for parallel reading if the agent supports sub-agents. **FORBIDDEN: browser sub-agents**.
+2. **UX Audit**: If the target involves UI, note it as a separate GitHub issue — do NOT block audit on visual inspection.
+3. **Compare**: Match docs + code findings to identify gaps/misalignments.
 
 ## 🚫 FORBIDDEN: NON-EXECUTION
 DO NOT edit/create/delete files, run commands, or implement code.

package/dist/prompts/root-cause-analysis.md

@@ -3,21 +3,22 @@ name: root-cause-analysis
 description: 5-Why analysis to trace bug origins.
 arguments:
   - name: tech_stack
-    description: Target tech stack.
-    required: true
+    description: Target tech stack. Optional — auto-detected from repo/context if omitted.
+    required: false
   - name: bug_description
-    description: Bug behavior.
-    required: true
+    description: Bug behavior. Optional — inferred from active task or recent conversation if omitted.
+    required: false
   - name: symptoms
     description: Logs, errors, metrics.
     required: false
 agent: Diagnostic Lead
 ---
-Conduct root cause analysis for repository bug.
+## 0. CONTEXT RESOLUTION
+- **tech_stack**: If provided, use directly. If omitted — detect from repo package files or active task tags.
+- **bug_description**: If provided, use directly. If omitted — extract from active task description or recent error/log context.
+- **symptoms**: Optional. Use if provided; otherwise infer from available logs or error traces.
 
-Stack: {{tech_stack}}
-Bug: {{bug_description}}
-Symptoms: {{symptoms}}
+Conduct root cause analysis for the active repository bug.
 
 Output:
 1. **Symptom**: Technical problem restatement.

package/dist/prompts/security-triage.md

@@ -3,21 +3,22 @@ name: security-triage
 description: Assess vulnerability exploitability and prioritize fix.
 arguments:
   - name: tech_stack
-    description: App stack.
-    required: true
+    description: App stack. Optional — auto-detected from repo/context if omitted.
+    required: false
   - name: vulnerability_report
-    description: Report details (CVE, SAST).
-    required: true
+    description: Report details (CVE, SAST). Optional — extracted from active task description or recent conversation if omitted.
+    required: false
   - name: codebase_context
     description: Usage context.
     required: false
 agent: Security Engineer
 ---
-Triage vulnerability for repository.
+## 0. CONTEXT RESOLUTION
+- **tech_stack**: If provided, use directly. If omitted — detect from repo package files, language, or active task tags.
+- **vulnerability_report**: If provided, use directly. If omitted — extract from active task description, recent conversation, or attached SAST output.
+- **codebase_context**: Optional. Use if provided.
 
-Stack: {{tech_stack}}
-Report: {{vulnerability_report}}
-Context: {{codebase_context}}
+Triage the resolved vulnerability for the active repository.
 
 Output:
 1. **Classification**: Type, CVE, CVSS, vector.

package/dist/prompts/senior-code-review.md

@@ -3,17 +3,18 @@ name: senior-code-review
 description: Comprehensive production-readiness evaluation.
 arguments:
   - name: tech_stack
-    description: Tech stack.
-    required: true
+    description: Tech stack. Optional — auto-detected from repo package files, language, or active task tags if omitted.
+    required: false
   - name: context
     description: Production context (SLA, data, conventions).
     required: false
 agent: Principal Reviewer
 ---
-Perform production-readiness review for repository.
+## 0. CONTEXT RESOLUTION
+- **tech_stack**: If provided, use directly. If omitted — detect from repo package files or language.
+- **context**: Optional. Use if provided; otherwise infer from task description or recent conversation.
 
-Stack: {{tech_stack}}
-Context: {{context}}
+Perform production-readiness review for the active repository.
 
 Audit Dimensions:
 1. **Errors**: Completeness & patterns.

package/dist/prompts/session-planner.md

@@ -3,11 +3,14 @@ name: session-planner
 description: Break objective into atomic tasks.
 arguments:
   - name: objective
-    description: High-level session goal.
-    required: true
+    description: High-level session goal. Optional — inferred from active task, recent conversation, or pending handoff if omitted.
+    required: false
 agent: Strategy Lead
 ---
-Plan execution for: '{{objective}}'.
+## 0. CONTEXT RESOLUTION
+- **objective**: If provided, use directly. If omitted — extract from the active `in_progress` task description, the most recent pending handoff, or the last user request in conversation context.
+
+Plan execution for the resolved objective.
 
 Steps:
 1. **Orient**: Call `task-list` to avoid duplicate active/backlog work.

package/dist/prompts/tech-affinity-scout.md

@@ -3,11 +3,14 @@ name: tech-affinity-scout
 description: Scout best practices from similar tech projects.
 arguments:
   - name: tags
-    description: CSV tech tags (e.g., 'react, tailwind').
-    required: true
+    description: CSV tech tags (e.g., 'react, tailwind'). Optional — auto-detected from repo package files, file extensions, or active task tags if omitted.
+    required: false
 agent: Tech Scout
 ---
-Scout for relevant knowledge using tags: [{{tags}}].
+## 0. CONTEXT RESOLUTION
+- **tags**: If provided, use directly. If omitted — detect from repo package files, file extensions, or active task tags.
+
+Scout for relevant knowledge using detected/provided tags.
 
 Steps:
 1. **Search**: Call `memory-search` with `current_tags=[{{tags}}]`.

package/dist/prompts/technical-planning.md

@@ -3,11 +3,14 @@ name: technical-planning
 description: Technical blueprint for new feature/product.
 arguments:
   - name: objective
-    description: High-level goal.
-    required: true
+    description: High-level goal. Optional — inferred from active task description, pending handoff, or recent conversation if omitted.
+    required: false
 agent: Technical Architect
 ---
-Create technical blueprint for: '{{objective}}'.
+## 0. CONTEXT RESOLUTION
+- **objective**: If provided, use directly. If omitted — extract from the active `in_progress` task description, the most recent pending handoff summary, or the last user instruction in conversation context.
+
+Create technical blueprint for the resolved objective.
 
 Cover:
 1. **Tech Stack**: Selected/confirmed technologies.

package/package.json

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