@vheins/local-memory-mcp 0.14.7 → 0.14.9

package/dist/{chunk-ODEGMBOP.js → chunk-UQZNTQJP.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.14.7") {
-  pkgVersion = "0.14.7";
+if ("0.14.9") {
+  pkgVersion = "0.14.9";
 } else {
   let searchDir = __dirname2;
   for (let i = 0; i < 5; i++) {

package/dist/dashboard/server.js

@@ -16,7 +16,7 @@ import {
   handleTaskClaim,
   listResources,
   logger
-} from "../chunk-ODEGMBOP.js";
+} from "../chunk-UQZNTQJP.js";
 
 // src/dashboard/server.ts
 import express from "express";

package/dist/mcp/server.js

@@ -60,7 +60,7 @@ import {
   toContextSlug,
   updateSessionFromInitialize,
   updateSessionRoots
-} from "../chunk-ODEGMBOP.js";
+} from "../chunk-UQZNTQJP.js";
 
 // src/mcp/server.ts
 import readline from "readline";

package/dist/prompts/architecture-design.md

@@ -14,20 +14,16 @@ category: planning
 tags: [architecture, system-design, components, data-flow, adr]
 ---
 
-# Skill: Architecture Design
+## FSM
 
-> Design system architecture for repository.
+Entry=S0 → S1 → S2 Exit=done
+Guard: S(N) req S(N-1)✅
 
-## I/O
-`tech_stack` (req), `requirements` (req) → `design/architecture/` (components, data flow, ADRs)
-
-## Rules
-- Component Diagram: Blocks & responsibilities
-- Data Flow: Information movement
-- ADRs: Rationale for patterns
-- Scalability/Reliability: Growth & failure handling
-- Security: Identity, protection, boundaries
+S0 | review tech_stack & requirements | — | component list, data flow map | —
+S1 | design: component diagram(blocks+responsibilities) + data flow(information movement) + ADRs(rationale) + scalability/reliability(growth+failure) + security(identity,protection,boundaries) | S0✅ | design decisions | —
+S2 | document artifacts | S1✅ | architecture docs | design/architecture/
 
 ## Chain
+
 ← N/A
-→ `architecture-documentation`: `design/architecture/` → as-built architecture doc
+→ architecture-documentation: design/architecture/ → as-built architecture doc

package/dist/prompts/create-task.md

@@ -3,98 +3,58 @@ name: create-task
 description: Create structured, atomic tasks in Local Memory MCP.
 arguments:
   - name: instruction
-    description: Directive to analyze and break into tasks. Optional — derived from active task, pending handoff, or recent conversation if omitted.
+    description: Directive to analyze and break into tasks. Derived from active task/pending handoff/recent conversation if omitted.
     required: false
 agent: Task Planner
-version: "1.0.0"
-license: Proprietary — Personal Use Only
 category: workflows
-type: Orchestrator
-complexity: Advanced
+version: "1.0.0"
 tags: [workflow, task-creation, planning, mcp]
-author: vheins
 ---
 
-## 🚫 FORBIDDEN: NON-EXECUTION
-DO NOT edit/create/delete files, run commands, or implement code.
-**Allowed**: Read code, `task-create`, `memory-store`, `task-list`, `memory-search`.
+## FSM
+
+Entry=S0 → S1 → S2 → S3  Exit=created
+Guard: S(N) req S(N-1)✅; NO code/edit/delete — MCP tools ONLY (allowed: task-create, task-list, task-detail, task-update, memory-store, memory-search, standard-search, standard-store, handoff-list, handoff-update, read)
 
-## ✅ OUTPUT: MCP ONLY
-ONLY call MCP tools. No prose, no code, no plans outside MCP.
+S0 | pre_analysis: memory-search(architecture/history) + standard-search(if task leads to code/test/refactor/migrate decisions) + handoff-list(pending; close stale that describe completed work) + read code(verify paths+impl) + task-list dedup(DO NOT duplicate; link via parent_id/depends_on) | — | context | —
+S1 | design tasks: atomic(1 logical change), layered(DB/Service/State/UI), context(paths+symbols+APIs), min 1 pos+1 neg test | S0✅ | task specs | —
+S2 | assign attributes: task_code(FEAT/FIX/REFACTOR-XXX), phase(Discovery|Implementation|Testing), priority(1=Low..5=Critical), strict description format | S1✅ | task attrs | —
+S3 | create via task-create(bulk max 500) + log decisions via memory-store(arch/feature changes; skip simple bugs) | S2✅ | MCP tasks created | —
+G1 | blueprint? | src=idea-to-blueprint | → route blueprint flow | —
+G2 | sprint? | src=.agents/documents/tasks/sprints/ | → route sprint flow | —
 
-## 1. PRE-ANALYSIS
-1. **Search Memory**: Call `memory-search` (architecture/history).
-2. **Search Standards**: Call `standard-search` for tasks that may lead to code edits, test edits, refactors, migrations, or implementation decisions. If no relevant standards are returned, note that no applicable standards were found.
-3. **Check Handoffs**: Call `handoff-list` for pending context that may already describe unfinished work. Ignore or close stale handoffs that only describe completed work.
-4. **Research Codebase**: Read relevant source files to verify current implementation and paths.
-5. **De-duplicate**: Call `task-list`. DO NOT duplicate existing tasks. Link related tasks via `parent_id`/`depends_on`.
+## Description Format (STRICT — used in S2)
 
-## 2. TASK DESIGN
-- **Atomic**: One logical change per task.
-- **Context**: Paths, symbols, APIs.
-- **Layered**: DB/Service/State/UI.
-- **Tests**: Min 1 Positive + 1 Negative.
+```
+### 1. Context & Analysis
+- **Trigger**: Instruction/finding.
+- **Observation**: Technical reasoning.
+- **Goal**: Clear objective.
+### 2. Step & Implementation
+- Detailed execution steps per path/layer.
+### 3. Acceptance & Verification
+- **Checklist**: `[ ]` criteria.
+- **Testing**: Scenarios.
+```
 
-## 3. ATTRIBUTES & FORMAT
-- `task_code`: FEAT/FIX/REFACTOR-XXX.
-- `phase`: Discovery/Implementation/Testing.
-- `priority`: 1-5 using this exact scale:
-  - `1 = Low`
-  - `2 = Normal`
-  - `3 = Medium`
-  - `4 = High`
-  - `5 = Critical`
-- `priority` is ascending by urgency. `5` is the highest urgency and `1` is the lowest. Never encode `Critical` as `1`.
-- `description` (STRICT FORMAT):
-  ### 1. Context & Analysis
-  - **Trigger**: Instruction/finding.
-  - **Observation**: Technical reasoning.
-  - **Goal**: Clear objective.
-  ### 2. Step & Implementation
-  - Detailed execution steps per path/layer.
-  ### 3. Acceptance & Verification
-  - **Checklist**: `[ ]` criteria.
-  - **Testing**: Scenarios.
+## Priority Scale
 
-## 4. MEMORY
-Log architectural/feature changes as `type: decision` via `memory-store`. Store reusable implementation rules via `standard-store`. Skip for simple bug fixes.
+`1=Low` `2=Normal` `3=Medium` `4=High` `5=Critical` (ascending urgency)
 
-## 5. MULTI-TASK
-- Parent/Child logic for complex directives.
-- Bulk limit: 500 records.
+## Blueprint Flow (G1→)
 
-## 5A. BLUEPRINT ORCHESTRATION IMPORT
-When the instruction source is `idea-to-blueprint`:
-- Create one root parent task for the full SDLC blueprint.
-- Create phase parent tasks for P0 through P10 and final no-gap handoff.
-- Create child tasks for every task breakdown row in the `idea-to-blueprint` skill.
-- Recursively decompose every referenced skill until leaf-level tasks are reached.
-- Preserve phase order with `depends_on`: P0 -> P1 -> G1 -> P2 -> G2 -> P3 -> G3 -> P4/P5 -> P6 -> P7 -> P8 -> P9 -> P10 -> GF.
-- For conditional tasks, create them with explicit condition metadata instead of omitting them:
-  - UI design tasks run when the product has UI.
-  - accessibility tests run when UI exists.
-  - performance/load tests run when capacity risk exists.
-  - database migration tests run when schema changes exist.
-  - microservice/monolith tasks run only when architecture context applies.
-- Gate tasks are internal quality checks. They should not ask for manual approval unless the gate is blocked by No-Go, missing mandatory input, or conflicting requirements.
-- All task descriptions must use the strict Context & Analysis, Step & Implementation, Acceptance & Verification format.
-- Call `task-list` before creation and link to existing related tasks instead of creating duplicates.
-- Store a decision memory summarizing the blueprint task graph and major assumptions.
+Root parent → phase parents P0..P10 → child tasks per breakdown row
+Recursive decompose every referenced skill to leaf level
+depends_on: P0→P1→G1→P2→G2→P3→G3→P4/P5→P6→P7→P8→P9→P10→GF
+Conditional tasks use metadata (not omission): UI design (if UI), a11y (if UI), perf (if capacity risk), db migration (if schema change), microservice (if arch context)
+Gates = internal quality checks; no manual approval unless blocked No-Go or missing mandatory input
+Store decision memory summarizing blueprint graph + assumptions
 
-## 5B. SPRINT PLAN IMPORT
-When the instruction source is `.agents/documents/tasks/sprints/`:
-- Treat sprint files and allocation audit as the source of truth.
-- Create one root parent task for the full delivery scope.
-- Create one sprint parent task per sprint and link each to the root via `parent_id`.
-- Create module/feature child tasks under the sprint where the work is scheduled.
-- Create atomic implementation/testing tasks under the matching module/feature parent.
-- Convert sprint dependency columns and implementation order into `depends_on`.
-- Preserve cross-sprint blockers by linking later sprint tasks to earlier sprint MCP task IDs.
-- Call `task-list` before creation and skip duplicates; link to existing related tasks instead.
-- Store a task creation audit in memory with created, linked, skipped duplicate, and blocked counts.
+## Sprint Flow (G2→)
 
-## 6. SELF-CHECK
-- ❌ No code/execution.
-- ✅ ONLY MCP tool calls.
+Root parent → sprint parents (per sprint) → module/feature children → atomic impl/test tasks
+Convert sprint dependency columns + implementation order into depends_on
+Preserve cross-sprint blockers via MCP task ID links
+Store creation audit: created, linked, skipped dup, blocked counts
 
 Analyze: {{instruction}}

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

@@ -6,63 +6,20 @@ arguments:
     description: Local path (file or directory) containing documentation or standards.
     required: true
 agent: Documentation Processor
-version: "1.0.0"
 category: workflows
+version: "1.0.0"
 tags: [workflow, csl, coding-standards, documentation, mcp]
 ---
 
-Fetch and convert local documentation from the provided path into atomic CSL (Coding Standards Library) entries for the coding_standards entity.
-
-Path: {{path}}
-Current repo: {{current_repo}}
-
-Goal:
-- Analyze the provided path.
-- If the path is a directory:
-  - Use the `list_directory` tool to list all files and subdirectories.
-  - Process each relevant file (e.g., .md, .txt, .js, .ts) sequentially.
-  - For each file, retrieve its content and extract standards.
-- If the path is a file:
-  - Use the `read_file` tool to retrieve the content of the file.
-  - Extract source-backed coding standards from the content.
-  - For each extracted rule, use the `standard-search` tool to check if a similar rule already exists (match by name or core instruction).
-  - Produce one atomic CSL entry per distinct rule that DOES NOT already exist.
-  - Each entry must be ready for the `standard-store` tool shape: name, content, parent_id, context, version, language, stack, tags, metadata, repo, is_global.
-
-Atomic entry rules:
-- One entry = one rule. Split bundled guidance into separate entries.
-- DO NOT emit duplicates. If `standard-search` returns a high-confidence match, skip the entry or update it if the new source is more authoritative.
-- Use parent/child only for genuine hierarchy: parent = umbrella principle, child = narrower enforceable specialization.
-- Keep content concise, imperative, and implementation-relevant.
-- ALWAYS include relevant code examples or snippets from the source that illustrate or enforce the rule. Do NOT discard code blocks.
-- Preserve the source meaning without inventing requirements.
-- Ignore boilerplate, non-normative text, or metadata noise. Do NOT ignore code examples.
-- Do not infer version, language, stack, or scope unless the source makes them explicit.
-- Use metadata to preserve provenance, including the original file path and a short evidence_excerpt for each entry.
+## FSM
 
-Output contract:
-- If tool calls are available:
-  - First, emit `standard-search` calls to verify existing data.
-  - Then, emit `standard-store` calls for every unique/new accepted entry.
-  - When parent/child hierarchy exists, emit the parent first, then emit children with `parent_id` referencing the created parent standard ID.
-- If tool calls are unavailable, return a JSON object with:
-  - `standards`: Array of `standard-store`-compatible payloads.
-- Use title-like names for the "name" field and store the atomic rule text along with its code examples in "content".
-- Use "context" for the topic area (for example: naming, error-handling, routing, testing, hooks, security).
-- Default version to "1.0.0" only when the source gives no versioning signal.
-- Prefer is_global=true unless the content is clearly repo-specific.
+Entry=G0 → S0 → S1 → S2 → S3  Exit=stored|refused
+Guard: S(N) req S(N-1)✅
 
-Refusal rules:
-- Refuse when the path does not exist or is not readable.
-- Refuse when the file content is not documentation or not clearly normative reference content.
-- Refuse when the request asks you to guess, invent, or fill missing guidance from prior knowledge.
-- Refuse when no source-backed coding standards can be extracted.
+G0 | path exists + readable + normative? | path provided? | → S0 / refuse | —
+S0 | discover: if dir→list_directory then read_file each; if file→read_file | G0✅ | raw content | —
+S1 | extract atomic rules: 1 entry=1 rule, keep code examples, split bundled, preserve source meaning, ignore boilerplate | S0✅ | atomic entries | —
+S2 | dedup via standard-search (skip if high-confidence match; update if new source more authoritative) | S1✅ | filtered entries | —
+S3 | store via standard-store: parent first→children with parent_id; context=topic area; version=1.0.0(default); is_global=true(unless repo-specific); metadata={original_path, evidence_excerpt} | S2✅ | CSL entries stored | —
 
-If you refuse, return exactly:
-```json
-{
-  "action": "refuse",
-  "reason": "<short explanation>",
-  "missing": ["<missing evidence or source requirement>"]
-}
-```
+Path: {{path}} Repo: {{current_repo}}

package/dist/prompts/csl-scrapper.md

@@ -6,62 +6,22 @@ arguments:
     description: Canonical URL for the documentation source to scrape.
     required: true
 agent: Documentation Scraper
-version: "1.0.0"
 category: workflows
+version: "1.0.0"
 tags: [workflow, csl, scraping, coding-standards, mcp]
 ---
 
-Fetch and convert trusted documentation from the provided URL into atomic CSL (Coding Standards Library) entries for the coding_standards entity.
-
-Source URL: {{source_url}}
-Current repo: {{current_repo}}
-
-Goal:
-- Use the web_fetch tool (if available) to retrieve the content of the provided Source URL.
-- Extract only source-backed coding standards from the documentation.
-- For each extracted rule, use the `standard-search` tool to check if a similar rule already exists (match by name or core instruction).
-- Produce one atomic CSL entry per distinct rule that DOES NOT already exist.
-- Each entry must be ready for the standard-store tool shape: name, content, parent_id, context, version, language, stack, tags, metadata, repo, is_global.
-- Identify documentation navigation menus (e.g., sidebars, index pages) containing links to related sub-pages. If present, create iterative scraping tasks for these sub-pages.
-- Detect documentation hierarchy when a page contains an umbrella rule with narrower sub-rules. In that case, emit one parent entry plus child entries linked with `parent_id`.
-
-Atomic entry rules:
-- One entry = one rule. Split bundled guidance into separate entries.
-- DO NOT emit duplicates. If `standard-search` returns a high-confidence match, skip the entry or update it if the new source is more authoritative.
-- Use parent/child only for genuine hierarchy: parent = umbrella principle, child = narrower enforceable specialization.
-- Keep content concise, imperative, and implementation-relevant.
-- ALWAYS include relevant code examples or snippets from the source that illustrate or enforce the rule. Do NOT discard code blocks.
-- Preserve the source meaning without inventing requirements.
-- Ignore marketing copy, release notes, and changelog noise. Do NOT ignore code examples.
-- Do not infer version, language, stack, or scope unless the source makes them explicit.
-- Use metadata to preserve provenance, including the source_url and a short evidence_excerpt for each entry.
+## FSM
 
-Output contract:
-- If tool calls are available:
-  - First, emit `standard-search` calls to verify existing data.
-  - Emit one `standard-store` call per unique/new accepted entry.
-  - When parent/child hierarchy exists, emit the parent first, then emit children with `parent_id` referencing the created parent standard ID.
-  - Emit one `task-create` call for each discovered documentation sub-page URL. The task title should be "Scrape: [URL]" and the description should instruct to use the `csl-scrapper` prompt for that URL.
-- If tool calls are unavailable, return a JSON object with:
-  - `standards`: Array of `standard-store`-compatible payloads.
-  - `next_urls`: Array of sub-page URLs to scrape.
-- Use title-like names for the "name" field and store the atomic rule text along with its code examples in "content".
-- Use "context" for the topic area (for example: naming, error-handling, routing, testing, hooks, security).
-- Use `parent_id` only when the source explicitly shows the rule is nested under a broader parent concept on the same page.
-- Default version to "1.0.0" only when the source gives no versioning signal.
-- Prefer is_global=true unless the source is clearly repo-specific.
+Entry=G0 → S0 → G1 → S1 → S2 → S3 → S4  Exit=stored|refused
+Guard: S(N) req S(N-1)✅
 
-Refusal rules:
-- Refuse when the URL content is not reachable, not documentation, or not clearly normative reference content.
-- Refuse when the source is too incomplete to verify atomic rules.
-- Refuse when the request asks you to guess, invent, or fill missing guidance from prior knowledge.
-- Refuse when no source-backed coding standards can be extracted.
+G0 | source_url provided? | source_url arg exists? | → S0 / refuse | —
+S0 | fetch via web_fetch | G0✅ | raw doc | —
+G1 | content reachable + normative? | S0✅ | → S1 / refuse | —
+S1 | extract atomic rules: 1 entry=1 rule, keep code examples, detect nav menus for sub-pages, ignore marketing/release notes, preserve source meaning | S0✅ | atomic entries, sub-page URLs | —
+S2 | dedup via standard-search (skip if high-confidence match; update if new source more authoritative) | S1✅ | filtered entries | —
+S3 | store via standard-store: parent first→children with parent_id; context=topic area; version=1.0.0(default); is_global=true(unless repo-specific); metadata={source_url, evidence_excerpt} | S2✅ | CSL entries stored | —
+S4 | create scrape tasks for each sub-page URL via task-create | sub-page URLs exist? | MCP tasks queued | —
 
-If you refuse, return exactly:
-```json
-{
-  "action": "refuse",
-  "reason": "<short explanation>",
-  "missing": ["<missing evidence or source requirement>"]
-}
-```
+Source: {{source_url}} Repo: {{current_repo}}

package/dist/prompts/documentation-sync.md

@@ -3,18 +3,17 @@ name: documentation-sync
 description: Sync memory decisions with repository markdown files
 arguments: []
 agent: Documentation Specialist
-version: "1.0.0"
-license: Proprietary — Personal Use Only
 category: workflows
-type: Utility
-complexity: Beginner
+version: "1.0.0"
 tags: [workflow, documentation, memory, sync]
-author: vheins
 ---
-Reconcile local documentation with stored memories.
 
-Steps:
-1. **Search**: Find `type: decision` memories via `memory-search`.
-2. **Scan**: Read `README.md`, `docs/`, `.agents/documents/`, and `.kiro/`.
-3. **Compare**: Identify missing or outdated durable knowledge.
-4. **Update**: Propose specific changes to align docs with current source of truth.
+## FSM
+
+Entry=S0 → S1 → S2 → S3 Exit=aligned
+Guard: S(N) req S(N-1)✅
+
+S0 | search decision memories via memory-search | — | memory entries | —
+S1 | read_file(README.md) + glob & read_file(docs/**/\*.md, .agents/documents/**/_, .kiro/\*\*/_) | S0✅ | doc content | —
+S2 | compare: identify missing/outdated knowledge | S1✅ | gap list | —
+S3 | propose specific changes to align docs | S2✅ | update proposals | —

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

@@ -12,33 +12,19 @@ arguments:
     description: Local task ID
     required: true
 agent: Integration Architect
-version: "1.0.0"
 category: workflows
+version: "1.0.0"
 tags: [workflow, github, task-sync, mcp]
 ---
 
-# Skill: export-task-to-github
-
-## 1. RETRIEVE
-1.  **Fetch**: Call `task-detail` for `task_id`.
-2.  **Verify**: Ensure title/description exist. Use `memory-search` for gaps.
-
-## 2. SYNC CHECK
-1.  **Search**: Use `search_issues` for `task_code`.
-2.  **De-duplicate**: If issue exists, update local task `metadata` with URL. DO NOT re-create.
-
-## 3. CREATE ISSUE
-If new:
--   **Write**: Use `issue_write` (method: 'create').
--   **Content**: Match local title/body exactly.
--   **Traceability**: Append `task_code` and `task_id` to body.
--   **Comments**: Post local comments via `add_issue_comment`.
+## FSM
 
-## 4. LINK
--   **Update**: Call `task-update`.
--   **Metadata**: Add GitHub URL.
--   **Comment**: "Exported to GitHub Issue #X".
+Entry=S0 → S1 → G1 → S2 → S3 → S4  Exit=exported|skipped
+Guard: S(N) req S(N-1)✅; MCP + GitHub tools ONLY
 
-## ✅ OUTPUT: MCP ONLY
-ONLY call: `task-detail`, `task-update`, `search_issues`, `issue_write`, `add_issue_comment`.
-No prose. No modifications to original content.
+S0 | fetch task via task-detail | task_id exists? | task data | —
+S1 | sync check via search_issues for task_code | S0✅ | existing issue? | —
+G1 | dedup gate — if exists→update local task metadata with URL, DO NOT re-create | S1✅ | exists→skip+link / new→S2 | —
+S2 | create issue via issue_write (match title/body, append task_code+id) | G1→new | GitHub issue created | —
+S3 | post comments via add_issue_comment | S2✅ | comments transferred | —
+S4 | link: task-update with GitHub URL + comment | S3✅ | task updated | —

package/dist/prompts/fix-suggestion.md

@@ -17,15 +17,21 @@ category: debugging
 tags: [fix, patch, bug-fix, code-change, test-case, debugging]
 ---
 
-# Skill: Fix Suggestion
+## FSM
 
-> Provide precise, minimal fix for confirmed bug.
+Entry=S0 → S1 Exit=suggestion
+Guard: S(N) req S(N-1)✅
+
+S0 | analyze inputs (tech_stack, bug_description, root_cause) | all req provided? | diagnosis | —
+S1 | produce: explanation + before/after diff(`diff ... `) + meta checklist + regression test | S0✅ | fix suggestion | —
+
+## Output Format (S1)
+
+- Explanation: Why bug happens + how fix works (prose)
+- Before/After: `diff blocks` with line comments
+- Meta checklist: config changes, migrations, dependencies
+- Verification: regression test case (code block)
 
 ## I/O
-tech_stack (req), bug_description (req), root_cause (req) → diagnosis report + fix suggestion
 
-## Rules
-1. Explanation: Why it happens and how fix works
-2. Before/After: Diff style code blocks with comments
-3. Checklist: Meta changes (config, migrations)
-4. Verification: Regression test case
+tech_stack + bug_description + root_cause → diagnosis report + fix suggestion

package/dist/prompts/import-github-issues.md

@@ -3,33 +3,18 @@ name: import-github-issues
 description: Import GitHub Issues as local tasks.
 arguments: []
 agent: Integration Scout
-version: "1.0.0"
-license: Proprietary — Personal Use Only
 category: workflows
-type: Orchestrator
-complexity: Intermediate
+version: "1.0.0"
 tags: [workflow, github, issue-import, mcp]
-author: vheins
 ---
 
-## 1. FETCH
--   **Primary**: Use `github-mcp-server` to list open issues.
--   **Fallback**: Terminal `gh issue list --json number,title,body,labels,url`.
-
-## 2. DE-DUPLICATE
--   **Scan**: Call `task-list`. Skip issues already existing as `GH-{{number}}` task codes.
-
-## 3. MAP & CREATE
-For each new issue, use `task-create`:
--   **`task_code`**: `GH-{{number}}`.
--   **`title` / `description`**: EXACT match from GitHub. DO NOT summarize.
--   **`tags`**: GitHub labels.
--   **`phase`**: `backlog` or `triage`.
--   **`metadata`**: include GitHub URL.
+## FSM
 
-## 4. COMMENTS
--   **Fetch**: Use `issue_read` (method='get_comments').
--   **Import**: Add comments to local task via `task-update`.
+Entry=S0 → S1 → S2 → S3 → S4  Exit=imported
+Guard: S(N) req S(N-1)✅
 
-## 5. SUMMARY
-Report count of tasks created.
+S0 | fetch open issues: primary=github-mcp-server; fallback=`gh issue list --json number,title,body,labels,url` | — | issue list | —
+S1 | dedup via task-list (skip if GH-{number} exists) | S0✅ | filtered issues | —
+S2 | create MCP tasks: task_code=GH-{number}, EXACT title/body (DO NOT summarize), tags=labels, phase=backlog|triage, metadata=URL | S1✅ | tasks created | —
+S3 | import comments via issue_read → task-update | S2✅ | comments linked | —
+S4 | report created count | S3✅ | summary | —

package/dist/prompts/learning-retrospective.md

@@ -6,19 +6,17 @@ arguments:
     description: ID of completed task.
     required: false
 agent: Knowledge Harvester
-version: "1.0.0"
 category: workflows
+version: "1.0.0"
 tags: [workflow, retrospective, memory, knowledge-management]
 ---
 
-Extract durable knowledge from task {{task_id}} for repository.
+## FSM
+
+Entry=S0 → S1  Exit=stored
+Guard: S(N) req S(N-1)✅
 
-Identify and `memory-store`:
-1. **Mistakes**: Hard-to-find bugs or environment quirks.
-2. **Decisions**: Trade-offs, library choices, architectural pivots.
-3. **Patterns**: Repeatable implementations or conventions.
+S0 | identify: mistakes (bugs/quirks), decisions (trade-offs/pivots), patterns (conventions) | task_id? | knowledge items | —
+S1 | store via memory-store (type=mistake|decision|pattern, include tech tags, concise) | S0✅ | durable memories | —
 
-Directives:
-- Use `type: mistake | decision | pattern`.
-- Include technology tags.
-- Keep content concise.
+Task: {{task_id}}

package/dist/prompts/memory-agent-core.md

@@ -3,38 +3,27 @@ name: memory-agent-core
 description: Behavioral contract for memory-aware agents.
 arguments: []
 agent: Memory Guardian
-version: "1.0.0"
-license: Proprietary — Personal Use Only
 category: workflows
-type: Utility
-complexity: Advanced
+version: "1.0.0"
 tags: [memory, workflow, guardrails, mcp]
-author: vheins
 ---
-# Memory Guardian Protocol
 
-You are a memory-aware agent. Memory is project truth, not a suggestion.
+## FSM — Execution Policy
+
+Entry=S0 → S1 → S2 → S3 → S4 → S5  Exit=act
+Guard: S(N) req S(N-1)✅; NEVER contradict stored decisions without memory-update or supersedes
 
-## Core Rules
-1. **Consistency**: Never contradict stored decisions without `memory-update` or `supersedes`.
-2. **Mistake Prevention**: Never repeat documented mistakes.
-3. **Affinity**: Only use cross-repo memory if tech tags match or it's marked `Global`.
-4. **Conflicts**: If memory clashes with user request, ask for clarification or propose `supersedes`.
-5. **Acknowledge**: After code generation using memory, you MUST call `memory-acknowledge`.
-6. **Search Mechanics**: Hybrid Search (70% Cosine, 30% BM25). 0.55 similarity threshold prevents duplication.
+S0 | orient: task-list + handoff-list (close stale pending) | session start? | active context | —
+S1 | claim: task-claim before work; claim-list/claim-release for stale | S0✅ | ownership | —
+S2 | search: memory-search(Hybrid: 70% Cosine+30% BM25, 0.55 threshold) + standard-search(task intent, lang, stack, repo) | S1✅ | relevant knowledge | —
+S3 | retrieve: memory-detail for full content if pointer rows insufficient | S2✅ | hydrated entries | —
+S4 | select: use ONLY highly relevant memories + standards | S3✅ | filtered knowledge | —
+S5 | acknowledge: after code gen using memory → memory-acknowledge(used|irrelevant|contradictory) | code generated? | feedback | —
 
-## Execution Policy
-1. **Orient**: Call `task-list` for active work and `handoff-list` for pending transfers when starting a repository session. Close stale pending handoffs with `handoff-update` when they no longer describe unfinished work.
-2. **Claim**: Use `task-claim` before taking ownership of a concrete task. Use `claim-list` when ownership is unclear and `claim-release` to clear stale claims during reassignment.
-3. **Search**: Call `memory-search` with `current_file_path` and `current_tags` before coding.
-4. **Standards**: Call `standard-search` before any code edit, test edit, refactor, migration, or implementation decision. Use the task intent, affected files, inferred language, stack, and repo as filters. If no relevant standards are returned, continue and state that no applicable standards were found.
-5. **Retrieve**: Use `memory-detail` for full content if search pointer rows are insufficient.
-6. **Select**: Use ONLY highly relevant memories and standards.
+## FSM — Creation Policy
 
-## Creation Policy
-Store memory ONLY if knowledge is durable (architecture, patterns, fixes) and affects future behavior.
-1. **Categorize**: Use technology `tags`.
-2. **Maintain**: Use `supersedes` for overrides.
-3. **Separate concerns**: Use `standard-store` for normative coding rules and `handoff-create`/`handoff-update` for agent transfer context. Do not store these as generic memories.
+Entry=S0 → S1  Exit=stored
+Guard: store ONLY if durable + affects future behavior; use supersedes for overrides
 
-Protect codebase health by respecting project history.
+S0 | categorize: type + tech tags; NEVER store coordination state (claims, file ownership) as memory | is durable? | classified | —
+S1 | store: memory-store(decisions/patterns) or standard-store(normative rules) or handoff-create(transfer ctx) | S0✅ | stored | —

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

@@ -6,16 +6,19 @@ arguments:
     description: File to review.
     required: true
 agent: Code Auditor
-version: "1.0.0"
 category: coding
+version: "1.0.0"
 tags: [code-review, memory, compliance, mcp]
 ---
 
-Audit {{file_path}} against stored project knowledge.
+## FSM
+
+Entry=S0 → S1 → S2 → S3  Exit=reviewed
+Guard: S(N) req S(N-1)✅
+
+S0 | search: memory-search (file_path) + standard-search (lang, stack, repo) | file_path provided? | relevant rules | —
+S1 | hydrate: memory-detail for relevant pointers | S0✅ | full rules | —
+S2 | evaluate compliance vs patterns, documented mistakes, standards | S1✅ | violation list | —
+S3 | feedback: suggest fixes citing source (memory|standard) | S2✅ | review report | —
 
-Steps:
-1. **Search Memory**: Call `memory-search` using `current_file_path='{{file_path}}'`.
-2. **Hydrate**: Call `memory-detail` for any relevant pointer row before enforcing it.
-3. **Search Standards**: Call `standard-search` with inferred language/stack/repo filters.
-4. **Evaluate**: Check for compliance with established patterns, documented mistakes, and applicable coding standards.
-5. **Feedback**: Suggest fixes for violations, citing whether the source is memory or standard.
+File: {{file_path}}