@kinqs/brainrouter-mcp-server 0.3.5 → 0.3.7

package/dist/memory/pipeline/task-queue.js

@@ -1,117 +0,0 @@
-/**
- * BrainRouter — Background Task Queue (Optimization C)
- *
- * Decouples L2 scene distillation and L3 persona distillation from the hot
- * path of capture(). These are the most expensive, non-latency-critical steps.
- *
- * Graph extraction (Opt B) fires immediately as fire-and-forget — it is NOT queued.
- * Contradiction detection (Opt A) also fires immediately as fire-and-forget.
- *
- * Flush triggers:
- *   1. Lazy — called by recall() when the user is idle (lastCapture > idleThresholdMs)
- *   2. Explicit — engine.flush(userId) called directly
- *   3. Disabled — BRAINROUTER_ASYNC_PIPELINE=false keeps old fire-and-forget behaviour
- */
-import { distillScenes } from "./l2-scene.js";
-import { distillPersona } from "./l3-distiller.js";
-// ─── Config ───────────────────────────────────────────────────────────────────
-/** Flush pending tasks before recall if last capture was more than this many ms ago. */
-const IDLE_THRESHOLD_MS = parseInt(process.env.BRAINROUTER_FLUSH_IDLE_MS ?? String(30_000), // default: 30s idle
-10);
-/** Is the async pipeline enabled? Default: true. Set to "false" to use old fire-and-forget. */
-export function isAsyncPipelineEnabled() {
-    return process.env.BRAINROUTER_ASYNC_PIPELINE !== "false";
-}
-// ─── Enqueue ──────────────────────────────────────────────────────────────────
-/**
- * Enqueue a task in the persistent SQLite queue instead of firing it immediately.
- * Safe to call from the capture hot path — synchronous SQLite insert, no I/O wait.
- */
-export function enqueueTask(store, task) {
-    const id = `task_${Date.now()}_${Math.random().toString(36).slice(2, 8)}`;
-    store.upsertPendingTask({
-        id,
-        userId: task.userId,
-        taskType: task.taskType,
-        payload: JSON.stringify(task.payload),
-        createdAt: new Date().toISOString(),
-    });
-}
-// ─── Flush ────────────────────────────────────────────────────────────────────
-/** Active flush promises per userId to prevent concurrent flushes */
-const flushInProgress = new Map();
-/**
- * Process all pending L2/L3 tasks for a user in FIFO order.
- *
- * Re-entrant safe: if a flush is already in progress for this userId, the existing
- * promise is returned instead of starting a second flush.
- */
-export async function flushPendingTasks(userId, store, synthesisRunner) {
-    const existing = flushInProgress.get(userId);
-    if (existing)
-        return existing;
-    const flushPromise = _doFlush(userId, store, synthesisRunner);
-    flushInProgress.set(userId, flushPromise);
-    try {
-        return await flushPromise;
-    }
-    finally {
-        flushInProgress.delete(userId);
-    }
-}
-async function _doFlush(userId, store, synthesisRunner) {
-    const start = Date.now();
-    const tasks = store.getPendingTasks(userId);
-    if (tasks.length === 0) {
-        return { userId, tasksProcessed: 0, tasksFailed: 0, durationMs: 0 };
-    }
-    let processed = 0;
-    let failed = 0;
-    // Process l2_scene and l3_persona in FIFO order.
-    // Deduplicate consecutive same-type tasks (e.g., 10 queued l2_scene → run once).
-    let lastTaskType = null;
-    for (const task of tasks) {
-        try {
-            if (task.taskType === lastTaskType) {
-                // Skip duplicate consecutive task of same type — one distillation run is sufficient
-                store.deletePendingTask(task.id);
-                continue;
-            }
-            switch (task.taskType) {
-                case "l2_scene":
-                    await distillScenes({ userId, store, llmRunner: synthesisRunner });
-                    break;
-                case "l3_persona":
-                    await distillPersona({ userId, store, llmRunner: synthesisRunner });
-                    break;
-            }
-            lastTaskType = task.taskType;
-            processed++;
-        }
-        catch (err) {
-            console.error(`[BrainRouter] Flush: task ${task.taskType} failed:`, err.message);
-            failed++;
-        }
-        finally {
-            store.deletePendingTask(task.id);
-        }
-    }
-    return {
-        userId,
-        tasksProcessed: processed,
-        tasksFailed: failed,
-        durationMs: Date.now() - start,
-    };
-}
-// ─── Idle Check ───────────────────────────────────────────────────────────────
-/**
- * Returns true if the user has been idle long enough that pre-recall flushing
- * won't noticeably delay the response.
- */
-export function isUserIdle(store, userId) {
-    const state = store.getSchedulerState(userId);
-    if (!state.lastCaptureAt)
-        return true; // never captured = trivially idle
-    const idleMs = Date.now() - new Date(state.lastCaptureAt).getTime();
-    return idleMs >= IDLE_THRESHOLD_MS;
-}

package/dist/memory/prompts/graph-extraction-batch.d.ts

@@ -1,14 +0,0 @@
-/**
- * Batch Graph Extraction Prompt
- *
- * Replaces N individual per-memory graph extraction calls with a single call
- * covering all new L1 memories from a capture cycle simultaneously.
- *
- * Token reduction: N → 1 call per capture cycle.
- */
-export declare const BATCH_GRAPH_EXTRACTION_SYSTEM_PROMPT = "You are an expert knowledge graph extraction engine.\n\nYou will receive a numbered list of memory statements. Extract ALL key entities (nodes)\nand their relationships (edges) across the entire list.\n\nLIMITS:\n- Extract at most 15 key entities total across all memories.\n- Extract at most 20 key relations total.\n- Focus on the most important technical choices, mandates, roles, and decisions.\n\nEntity Types:\n- \"tool\" / \"technology\" (e.g. pnpm, React, Postgres, Zod)\n- \"project\" (e.g. BrainRouter, Kinqs Radio)\n- \"person\" (e.g. lead engineer, user, junior developers)\n- \"concept\" / \"decision\" (e.g. monorepo migration, dark mode, camelCase policy)\n\nRelation Types (use ONLY these):\n- \"uses\" / \"adopts\"\n- \"owns\" / \"manages\"\n- \"decided\" / \"revised\"\n- \"conflicts_with\" / \"replaces\"\n- \"applies_to\"\n- \"requires\"\n- \"is_a\" / \"is_role\"\n\nFor each entity, also include \"sourceIndex\" matching the memory's index number.\n\nOutput ONLY a valid JSON object (no markdown fences):\n{\n  \"entities\": [\n    { \"entity\": \"Canonical Name\", \"type\": \"tool|technology|project|person|concept|decision\", \"confidence\": 1.0, \"sourceIndex\": 0 }\n  ],\n  \"relations\": [\n    { \"from\": \"Entity A\", \"to\": \"Entity B\", \"relation\": \"uses\", \"confidence\": 1.0 }\n  ]\n}";
-export declare function formatBatchGraphExtractionPrompt(memories: Array<{
-    index: number;
-    content: string;
-    recordId: string;
-}>): string;

package/dist/memory/prompts/graph-extraction-batch.js

@@ -1,54 +0,0 @@
-/**
- * Batch Graph Extraction Prompt
- *
- * Replaces N individual per-memory graph extraction calls with a single call
- * covering all new L1 memories from a capture cycle simultaneously.
- *
- * Token reduction: N → 1 call per capture cycle.
- */
-export const BATCH_GRAPH_EXTRACTION_SYSTEM_PROMPT = `You are an expert knowledge graph extraction engine.
-
-You will receive a numbered list of memory statements. Extract ALL key entities (nodes)
-and their relationships (edges) across the entire list.
-
-LIMITS:
-- Extract at most 15 key entities total across all memories.
-- Extract at most 20 key relations total.
-- Focus on the most important technical choices, mandates, roles, and decisions.
-
-Entity Types:
-- "tool" / "technology" (e.g. pnpm, React, Postgres, Zod)
-- "project" (e.g. BrainRouter, Kinqs Radio)
-- "person" (e.g. lead engineer, user, junior developers)
-- "concept" / "decision" (e.g. monorepo migration, dark mode, camelCase policy)
-
-Relation Types (use ONLY these):
-- "uses" / "adopts"
-- "owns" / "manages"
-- "decided" / "revised"
-- "conflicts_with" / "replaces"
-- "applies_to"
-- "requires"
-- "is_a" / "is_role"
-
-For each entity, also include "sourceIndex" matching the memory's index number.
-
-Output ONLY a valid JSON object (no markdown fences):
-{
-  "entities": [
-    { "entity": "Canonical Name", "type": "tool|technology|project|person|concept|decision", "confidence": 1.0, "sourceIndex": 0 }
-  ],
-  "relations": [
-    { "from": "Entity A", "to": "Entity B", "relation": "uses", "confidence": 1.0 }
-  ]
-}`;
-export function formatBatchGraphExtractionPrompt(memories) {
-    const memoryList = memories
-        .map(m => `  [${m.index}] "${m.content}"`)
-        .join("\n");
-    return `Extract entities and relations from ALL of the following memories:
-
-${memoryList}
-
-JSON Output:`;
-}

package/dist/memory/prompts/l1-contradiction-batch.d.ts

@@ -1,16 +0,0 @@
-/**
- * Batch Contradiction Detection Prompt
- *
- * Replaces N×K individual pairwise LLM calls with a single call covering
- * all new memories and their top FTS candidates simultaneously.
- *
- * Token reduction: 25 → 1 call per capture cycle (for 5 new memories × 5 candidates).
- */
-export declare const BATCH_CONTRADICTION_SYSTEM_PROMPT = "You are the Contradiction & Temporal Update Detector for a hierarchical memory engine.\n\nYou will receive a list of NEWLY EXTRACTED memories and a list of EXISTING memories.\nYour task is to identify ALL pairs that contradict, supersede, or update each other.\n\nRULES:\n1. Only flag pairs with genuine overlap or conflict. Ignore unrelated pairs.\n2. Classify each contradiction into one of two kinds:\n   - \"temporal_update\": The new memory deliberately supersedes the old one (e.g. user changed their mind, moved cities, switched tools). The NEW memory wins.\n   - \"genuine_conflict\": Logically incompatible absolute claims where neither obviously supersedes the other (e.g. conflicting birth years).\n3. Provide a confidence score (0.0\u20131.0). Only include pairs with confidence > 0.7.\n4. If no contradictions exist, return an empty array.\n\nRespond ONLY with a JSON array (no markdown fences):\n[\n  {\n    \"newIndex\": number,\n    \"existingIndex\": number,\n    \"kind\": \"temporal_update\" | \"genuine_conflict\",\n    \"reason\": \"Brief explanation\",\n    \"confidence\": number\n  }\n]";
-export declare function formatBatchContradictionPrompt(newMemories: Array<{
-    index: number;
-    content: string;
-}>, existingMemories: Array<{
-    index: number;
-    content: string;
-}>): string;

package/dist/memory/prompts/l1-contradiction-batch.js

@@ -1,47 +0,0 @@
-/**
- * Batch Contradiction Detection Prompt
- *
- * Replaces N×K individual pairwise LLM calls with a single call covering
- * all new memories and their top FTS candidates simultaneously.
- *
- * Token reduction: 25 → 1 call per capture cycle (for 5 new memories × 5 candidates).
- */
-export const BATCH_CONTRADICTION_SYSTEM_PROMPT = `You are the Contradiction & Temporal Update Detector for a hierarchical memory engine.
-
-You will receive a list of NEWLY EXTRACTED memories and a list of EXISTING memories.
-Your task is to identify ALL pairs that contradict, supersede, or update each other.
-
-RULES:
-1. Only flag pairs with genuine overlap or conflict. Ignore unrelated pairs.
-2. Classify each contradiction into one of two kinds:
-   - "temporal_update": The new memory deliberately supersedes the old one (e.g. user changed their mind, moved cities, switched tools). The NEW memory wins.
-   - "genuine_conflict": Logically incompatible absolute claims where neither obviously supersedes the other (e.g. conflicting birth years).
-3. Provide a confidence score (0.0–1.0). Only include pairs with confidence > 0.7.
-4. If no contradictions exist, return an empty array.
-
-Respond ONLY with a JSON array (no markdown fences):
-[
-  {
-    "newIndex": number,
-    "existingIndex": number,
-    "kind": "temporal_update" | "genuine_conflict",
-    "reason": "Brief explanation",
-    "confidence": number
-  }
-]`;
-export function formatBatchContradictionPrompt(newMemories, existingMemories) {
-    const newList = newMemories
-        .map(m => `  [N${m.index}] "${m.content}"`)
-        .join("\n");
-    const existingList = existingMemories
-        .map(m => `  [E${m.index}] "${m.content}"`)
-        .join("\n");
-    return `NEWLY EXTRACTED MEMORIES:
-${newList}
-
-EXISTING MEMORIES (candidates for contradiction):
-${existingList}
-
-Identify all contradicting pairs between the N (new) and E (existing) sets.
-JSON Array Output:`;
-}

package/dist/memory/prompts/l1-contradiction.d.ts

@@ -1 +0,0 @@
-export declare const L1_CONTRADICTION_PROMPT = "\nYou are the Contradiction & Temporal Update Detector for a hierarchical memory engine.\nYour task is to compare a NEWLY EXTRACTED memory with an EXISTING RELEVANT memory and determine if they contradict, supersede, or update each other.\n\nNEW MEMORY:\n\"{{newContent}}\"\n\nEXISTING MEMORY:\n\"{{existingContent}}\"\n\nRULES:\n1. Determine if they overlap or conflict. If there is no overlap/conflict, set \"isContradiction\" to false.\n2. If they conflict or override, classify the relationship into one of two kinds:\n   - \"temporal_update\": The new memory is a deliberate update, change of mind, transition, or correction to the old memory (e.g. \"User lives in SF\" vs \"User moved to NYC\", or \"User wants pnpm\" vs \"User changed package manager to regular npm\"). This means the new memory actively supersedes the old one.\n   - \"genuine_conflict\": The statements are logically incompatible, absolute claims that cannot both be true, and it is NOT a simple update or transition (e.g. \"User was born in 1990\" vs \"User was born in 1995\", or conflicting rules without a clear indication that one was meant to update the other).\n3. Provide a clear reason and a confidence score.\n\nRespond ONLY with a JSON object:\n{\n  \"isContradiction\": boolean,\n  \"kind\": \"temporal_update\" | \"genuine_conflict\" | null,\n  \"reason\": \"Brief explanation if isContradiction is true, else null\",\n  \"confidence\": number (0.0 to 1.0)\n}\n";

package/dist/memory/prompts/l1-contradiction.js

@@ -1,25 +0,0 @@
-export const L1_CONTRADICTION_PROMPT = `
-You are the Contradiction & Temporal Update Detector for a hierarchical memory engine.
-Your task is to compare a NEWLY EXTRACTED memory with an EXISTING RELEVANT memory and determine if they contradict, supersede, or update each other.
-
-NEW MEMORY:
-"{{newContent}}"
-
-EXISTING MEMORY:
-"{{existingContent}}"
-
-RULES:
-1. Determine if they overlap or conflict. If there is no overlap/conflict, set "isContradiction" to false.
-2. If they conflict or override, classify the relationship into one of two kinds:
-   - "temporal_update": The new memory is a deliberate update, change of mind, transition, or correction to the old memory (e.g. "User lives in SF" vs "User moved to NYC", or "User wants pnpm" vs "User changed package manager to regular npm"). This means the new memory actively supersedes the old one.
-   - "genuine_conflict": The statements are logically incompatible, absolute claims that cannot both be true, and it is NOT a simple update or transition (e.g. "User was born in 1990" vs "User was born in 1995", or conflicting rules without a clear indication that one was meant to update the other).
-3. Provide a clear reason and a confidence score.
-
-Respond ONLY with a JSON object:
-{
-  "isContradiction": boolean,
-  "kind": "temporal_update" | "genuine_conflict" | null,
-  "reason": "Brief explanation if isContradiction is true, else null",
-  "confidence": number (0.0 to 1.0)
-}
-`;

package/dist/memory/prompts/l1-extraction.d.ts

@@ -1,10 +0,0 @@
-import type { L0Record } from "@brainrouter/types";
-export declare const EXTRACT_MEMORIES_SYSTEM_PROMPT = "You are a Skill-Aware Memory Extraction Expert for a software engineering AI assistant.\n\nYour task is to analyze a conversation and extract durable, self-contained memories.\n\n### Scene Segmentation\nDetermine if the topic has changed since the previous scene.\nIf there are existing scenes, PREFER to reuse the most relevant existing scene name \u2014 only create a new name if the topic is genuinely different from ALL existing scenes.\nIf reusing, use the EXACT existing name (no paraphrasing).\nIf creating new, format: \"AI helping [user role] with [goal activity]\" (unique, max 50 chars).\n\n### Memory Types\n\n1. **persona** \u2014 Stable user traits, preferences, identity\n   - Format: \"User [prefers/is/always/never] ...\"\n   - Priority: 80-100 (core identity) / 50-70 (preferences) / skip if <50\n\n2. **episodic** \u2014 Objective events, decisions, results with timestamps\n   - Format: \"User [did X] at [time] resulting in [Y]\"\n   - Priority: 80-100 (major decisions) / 60-79 (significant events) / skip if <60\n\n3. **instruction** \u2014 Long-term rules the user gave the AI\n   - Format: \"User requires AI to always/never ...\"\n   - Priority: 90-100 (hard rules) / 70-89 (preferences) / skip if <70\n   - Instructions NEVER decay.\n\n4. **skill_context** \u2014 Observations about how the user runs THIS SKILL specifically\n   - Format: \"When running [skill], user tends to ...\"\n   - Only extract if a genuine behavioral pattern is visible, not a one-off.\n\n5. **tool_preference** \u2014 Stable preferences about tools, workflows, or command usage.\n6. **codebase_fact / api_contract / data_model** \u2014 Verified facts about code, public APIs, schemas, or storage models.\n7. **dependency_constraint / environment_constraint** \u2014 Version, runtime, platform, sandbox, or deployment constraints.\n8. **architecture_decision / implementation_decision / design_constraint** \u2014 Durable decisions and constraints that future agents must preserve.\n9. **security_policy / performance_baseline** \u2014 Security rules or measured performance facts. Extract only with direct evidence.\n10. **bug_finding / debug_trace / fix_summary / verification_result / failed_attempt / regression_risk** \u2014 Debugging history, fixes, checks, and risk notes.\n11. **task_state / handover_note / blocked_reason / review_comment / release_note** \u2014 Planning, review, release, and continuation state.\n12. **source_evidence / artifact_reference / file_history / command_knowledge** \u2014 Evidence-backed references to files, artifacts, file evolution, or command behavior.\n\nAllowed type values:\npersona, episodic, instruction, skill_context, tool_preference, codebase_fact, api_contract,\ndata_model, dependency_constraint, environment_constraint, architecture_decision,\nimplementation_decision, design_constraint, security_policy, performance_baseline,\nbug_finding, debug_trace, fix_summary, verification_result, failed_attempt, regression_risk,\ntask_state, handover_note, blocked_reason, review_comment, release_note, source_evidence,\nartifact_reference, file_history, command_knowledge.\n\n### Quality Rules\n- Nothingness > Bad memory. Prefer empty over wrong.\n- Memory must stand alone without the conversation.\n- Merge causally-linked facts into one memory.\n- Do not extract AI outputs \u2014 only user behavior and statements.\n- Filter out: tool calls, one-time requests, casual greetings.\n- Evidence-gated types (api_contract, data_model, security_policy, performance_baseline) require a cited file path, command, test result, or explicit user statement.\n- Use confidence from 0.0 to 1.0. Use lower confidence for model inference, higher confidence for direct source or command output.\n- Classify sourceKind as user_instruction, source_file, command_output, test_result, model_inference, or prior_memory.\n- Extract filePaths, repoPaths, and commands when explicitly mentioned; otherwise use empty arrays.\n\n### Output\nReturn ONLY a valid JSON array matching this format exactly:\n[\n  {\n    \"scene_name\": \"current or inherited scene name\",\n    \"message_ids\": [\"id1\"],\n    \"memories\": [\n      {\n        \"type\": \"one allowed type value\",\n        \"content\": \"self-contained memory statement\",\n        \"priority\": 85,\n        \"skill_tag\": \"the active skill\",\n        \"source_message_ids\": [\"id1\"],\n        \"confidence\": 0.75,\n        \"sourceKind\": \"user_instruction|source_file|command_output|test_result|model_inference|prior_memory\",\n        \"verificationStatus\": \"verified|unverified|stale\",\n        \"repoPaths\": [],\n        \"filePaths\": [],\n        \"commands\": [],\n        \"metadata\": {}\n      }\n    ]\n  }\n]\n";
-export declare function formatExtractionPrompt(params: {
-    newMessages: L0Record[];
-    backgroundMessages?: L0Record[];
-    previousSceneName?: string;
-    existingSceneNames?: string[];
-    activeSkill?: string;
-    skillHints?: string;
-}): string;

package/dist/memory/prompts/l1-extraction.js

@@ -1,114 +0,0 @@
-// ============================
-// System Prompt
-// ============================
-export const EXTRACT_MEMORIES_SYSTEM_PROMPT = `You are a Skill-Aware Memory Extraction Expert for a software engineering AI assistant.
-
-Your task is to analyze a conversation and extract durable, self-contained memories.
-
-### Scene Segmentation
-Determine if the topic has changed since the previous scene.
-If there are existing scenes, PREFER to reuse the most relevant existing scene name — only create a new name if the topic is genuinely different from ALL existing scenes.
-If reusing, use the EXACT existing name (no paraphrasing).
-If creating new, format: "AI helping [user role] with [goal activity]" (unique, max 50 chars).
-
-### Memory Types
-
-1. **persona** — Stable user traits, preferences, identity
-   - Format: "User [prefers/is/always/never] ..."
-   - Priority: 80-100 (core identity) / 50-70 (preferences) / skip if <50
-
-2. **episodic** — Objective events, decisions, results with timestamps
-   - Format: "User [did X] at [time] resulting in [Y]"
-   - Priority: 80-100 (major decisions) / 60-79 (significant events) / skip if <60
-
-3. **instruction** — Long-term rules the user gave the AI
-   - Format: "User requires AI to always/never ..."
-   - Priority: 90-100 (hard rules) / 70-89 (preferences) / skip if <70
-   - Instructions NEVER decay.
-
-4. **skill_context** — Observations about how the user runs THIS SKILL specifically
-   - Format: "When running [skill], user tends to ..."
-   - Only extract if a genuine behavioral pattern is visible, not a one-off.
-
-5. **tool_preference** — Stable preferences about tools, workflows, or command usage.
-6. **codebase_fact / api_contract / data_model** — Verified facts about code, public APIs, schemas, or storage models.
-7. **dependency_constraint / environment_constraint** — Version, runtime, platform, sandbox, or deployment constraints.
-8. **architecture_decision / implementation_decision / design_constraint** — Durable decisions and constraints that future agents must preserve.
-9. **security_policy / performance_baseline** — Security rules or measured performance facts. Extract only with direct evidence.
-10. **bug_finding / debug_trace / fix_summary / verification_result / failed_attempt / regression_risk** — Debugging history, fixes, checks, and risk notes.
-11. **task_state / handover_note / blocked_reason / review_comment / release_note** — Planning, review, release, and continuation state.
-12. **source_evidence / artifact_reference / file_history / command_knowledge** — Evidence-backed references to files, artifacts, file evolution, or command behavior.
-
-Allowed type values:
-persona, episodic, instruction, skill_context, tool_preference, codebase_fact, api_contract,
-data_model, dependency_constraint, environment_constraint, architecture_decision,
-implementation_decision, design_constraint, security_policy, performance_baseline,
-bug_finding, debug_trace, fix_summary, verification_result, failed_attempt, regression_risk,
-task_state, handover_note, blocked_reason, review_comment, release_note, source_evidence,
-artifact_reference, file_history, command_knowledge.
-
-### Quality Rules
-- Nothingness > Bad memory. Prefer empty over wrong.
-- Memory must stand alone without the conversation.
-- Merge causally-linked facts into one memory.
-- Do not extract AI outputs — only user behavior and statements.
-- Filter out: tool calls, one-time requests, casual greetings.
-- Evidence-gated types (api_contract, data_model, security_policy, performance_baseline) require a cited file path, command, test result, or explicit user statement.
-- Use confidence from 0.0 to 1.0. Use lower confidence for model inference, higher confidence for direct source or command output.
-- Classify sourceKind as user_instruction, source_file, command_output, test_result, model_inference, or prior_memory.
-- Extract filePaths, repoPaths, and commands when explicitly mentioned; otherwise use empty arrays.
-
-### Output
-Return ONLY a valid JSON array matching this format exactly:
-[
-  {
-    "scene_name": "current or inherited scene name",
-    "message_ids": ["id1"],
-    "memories": [
-      {
-        "type": "one allowed type value",
-        "content": "self-contained memory statement",
-        "priority": 85,
-        "skill_tag": "the active skill",
-        "source_message_ids": ["id1"],
-        "confidence": 0.75,
-        "sourceKind": "user_instruction|source_file|command_output|test_result|model_inference|prior_memory",
-        "verificationStatus": "verified|unverified|stale",
-        "repoPaths": [],
-        "filePaths": [],
-        "commands": [],
-        "metadata": {}
-      }
-    ]
-  }
-]
-`;
-// ============================
-// Prompt Builder
-// ============================
-export function formatExtractionPrompt(params) {
-    const { newMessages, backgroundMessages = [], previousSceneName = "None", existingSceneNames = [], activeSkill = "None", skillHints = "None" } = params;
-    const bgText = backgroundMessages.length > 0
-        ? backgroundMessages
-            .map((m) => `[${m.id}] [${m.role}] [${new Date(m.timestamp).toISOString()}]: ${m.messageText}`)
-            .join("\n\n")
-        : "None";
-    const newText = newMessages
-        .map((m) => `[${m.id}] [${m.role}] [${new Date(m.timestamp).toISOString()}]: ${m.messageText}`)
-        .join("\n\n");
-    const existingScenesNote = existingSceneNames.length > 0
-        ? `[EXISTING SCENES] (reuse one of these if the topic matches):\n${existingSceneNames.map(n => `  - ${n}`).join("\n")}`
-        : "[EXISTING SCENES]: None yet";
-    return `[PREVIOUS SCENE]: ${previousSceneName}
-${existingScenesNote}
-[ACTIVE SKILL]: ${activeSkill}
-[SKILL EXTRACTION HINTS]: ${skillHints}
-
-[BACKGROUND CONVERSATION] (Context only, DO NOT extract from here):
-${bgText}
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-[NEW MESSAGES TO EXTRACT FROM] (Extract memories ONLY from here):
-${newText}`;
-}

package/dist/memory/prompts/l2-direction-shift.d.ts

@@ -1,5 +0,0 @@
-export declare const L2_DIRECTION_SHIFT_SYSTEM_PROMPT = "You are a context analyzer for a software engineering AI assistant.\n\nYour task is to determine if a new batch of memories represents a MAJOR shift away from the current active scene (topic/feature), or if it's a continuation of the same work.\n\nA major shift means:\n- The user has moved to a completely different feature, bug, or module.\n- The context of the active scene is no longer primarily relevant.\n\nA continuation means:\n- They are fixing bugs related to the active scene.\n- They are writing tests for the active scene.\n- They are continuing work on the active scene.\n\nOutput ONLY a JSON object with this exact schema:\n{\n  \"shift\": boolean,\n  \"confidence\": number (0.0 to 1.0),\n  \"reason\": \"short explanation\"\n}";
-export declare function formatL2DirectionShiftPrompt(activeScene: string, activeSceneSummary: string, newMemories: Array<{
-    content: string;
-    type: string;
-}>): string;

package/dist/memory/prompts/l2-direction-shift.js

@@ -1,32 +0,0 @@
-// ============================
-// L2 Direction Shift Detection Prompt
-// ============================
-export const L2_DIRECTION_SHIFT_SYSTEM_PROMPT = `You are a context analyzer for a software engineering AI assistant.
-
-Your task is to determine if a new batch of memories represents a MAJOR shift away from the current active scene (topic/feature), or if it's a continuation of the same work.
-
-A major shift means:
-- The user has moved to a completely different feature, bug, or module.
-- The context of the active scene is no longer primarily relevant.
-
-A continuation means:
-- They are fixing bugs related to the active scene.
-- They are writing tests for the active scene.
-- They are continuing work on the active scene.
-
-Output ONLY a JSON object with this exact schema:
-{
-  "shift": boolean,
-  "confidence": number (0.0 to 1.0),
-  "reason": "short explanation"
-}`;
-export function formatL2DirectionShiftPrompt(activeScene, activeSceneSummary, newMemories) {
-    const memLines = newMemories.map(m => `- [${m.type}] ${m.content}`).join("\n");
-    return `### Active Scene: ${activeScene}
-${activeSceneSummary}
-
-### New Memories:
-${memLines}
-
-Does the new batch of memories represent a major shift away from the active scene? Return JSON.`;
-}

package/dist/memory/prompts/l2-scene-cluster.d.ts

@@ -1,2 +0,0 @@
-export declare const L2_SCENE_CLUSTER_SYSTEM_PROMPT = "You are a semantic text clustering expert for an AI agent's memory database.\n\nYour task is to review a list of work scene/session names and identify near-duplicate or highly overlapping scenes that should be merged to prevent memory fragmentation.\n\nRules:\n1. Group scenes that discuss the SAME overall goal, project, or task (e.g., \"monorepo migration setup\", \"monorepo architecture\", \"monorepo setup\" should all be one cluster).\n2. For each cluster, pick or write one clean, professional, and descriptive \"canonical\" name (e.g. \"AI helping lead engineer with monorepo architecture setup\").\n3. Put the near-duplicate scene names into the \"aliases\" array.\n4. If a scene does not have any duplicates or overlaps, you can skip including it, or place it in its own cluster with an empty aliases list.\n5. Every alias must be exactly as it appears in the input list.\n\nReturn ONLY a valid JSON array matching this format exactly:\n[\n  {\n    \"canonical\": \"AI helping lead engineer with monorepo architecture setup\",\n    \"aliases\": [\n      \"AI helping lead engineer with monorepo setup\",\n      \"AI helping Lead Engineer with Monorepo Architecture Migration\"\n    ]\n  }\n]\n";
-export declare function formatSceneClusterPrompt(sceneNames: string[]): string;

package/dist/memory/prompts/l2-scene-cluster.js

@@ -1,33 +0,0 @@
-// ============================
-// L2 Scene Clustering & Canonicalization Prompt
-// ============================
-export const L2_SCENE_CLUSTER_SYSTEM_PROMPT = `You are a semantic text clustering expert for an AI agent's memory database.
-
-Your task is to review a list of work scene/session names and identify near-duplicate or highly overlapping scenes that should be merged to prevent memory fragmentation.
-
-Rules:
-1. Group scenes that discuss the SAME overall goal, project, or task (e.g., "monorepo migration setup", "monorepo architecture", "monorepo setup" should all be one cluster).
-2. For each cluster, pick or write one clean, professional, and descriptive "canonical" name (e.g. "AI helping lead engineer with monorepo architecture setup").
-3. Put the near-duplicate scene names into the "aliases" array.
-4. If a scene does not have any duplicates or overlaps, you can skip including it, or place it in its own cluster with an empty aliases list.
-5. Every alias must be exactly as it appears in the input list.
-
-Return ONLY a valid JSON array matching this format exactly:
-[
-  {
-    "canonical": "AI helping lead engineer with monorepo architecture setup",
-    "aliases": [
-      "AI helping lead engineer with monorepo setup",
-      "AI helping Lead Engineer with Monorepo Architecture Migration"
-    ]
-  }
-]
-`;
-export function formatSceneClusterPrompt(sceneNames) {
-    return `Please analyze the following list of scene names and group any near-duplicates or highly overlapping topics into clusters.
-
-### Input Scene Names:
-${sceneNames.map(s => `- ${s}`).join("\n")}
-
-### Output Format (strict JSON array of clusters):`;
-}

package/dist/memory/prompts/l2-scene.d.ts

@@ -1,7 +0,0 @@
-export declare const L2_SCENE_SYSTEM_PROMPT = "You are a technical memory summarizer for a software engineering AI assistant.\n\nYour task is to synthesize a set of extracted memories about a specific work session into a concise, durable Scene Summary.\n\nThe summary must:\n- Be written as Markdown\n- Be accurate and grounded only in the provided memories \u2014 do NOT infer or fabricate\n- Be self-contained (readable without the original conversation)\n- Capture what was being worked on, key decisions, and outcomes\n- Be 2-4 sentences for the main summary, plus short bullet lists\n\nOutput ONLY the Markdown. No preamble, no explanation.";
-export declare function formatL2ScenePrompt(sceneName: string, memories: Array<{
-    content: string;
-    type: string;
-    priority: number;
-    skill_tag: string;
-}>, existingSceneNames?: string[]): string;

package/dist/memory/prompts/l2-scene.js

@@ -1,40 +0,0 @@
-// ============================
-// L2 Scene Summary Prompt
-// ============================
-export const L2_SCENE_SYSTEM_PROMPT = `You are a technical memory summarizer for a software engineering AI assistant.
-
-Your task is to synthesize a set of extracted memories about a specific work session into a concise, durable Scene Summary.
-
-The summary must:
-- Be written as Markdown
-- Be accurate and grounded only in the provided memories — do NOT infer or fabricate
-- Be self-contained (readable without the original conversation)
-- Capture what was being worked on, key decisions, and outcomes
-- Be 2-4 sentences for the main summary, plus short bullet lists
-
-Output ONLY the Markdown. No preamble, no explanation.`;
-export function formatL2ScenePrompt(sceneName, memories, existingSceneNames = []) {
-    const memLines = memories
-        .map(m => `- [${m.type}${m.skill_tag ? `|${m.skill_tag}` : ""}] ${m.content}`)
-        .join("\n");
-    const existingNote = existingSceneNames.length > 0
-        ? `\n### Existing Scenes (for your context — avoid duplicating these):\n${existingSceneNames.map(s => `- ${s}`).join("\n")}`
-        : "";
-    return `Generate a Scene Summary for the following work session.${existingNote}
-
-## Scene: ${sceneName}
-
-### Extracted Memories:
-${memLines}
-
-### Output Format (strict Markdown):
-## ${sceneName}
-**Summary**: [2-3 sentence distillation of what happened and the outcome]
-
-**Key Decisions**:
-- [decision 1]
-- [decision 2]
-
-**Skills Active**: [comma-separated skill names, or "none" if absent]
-**Memory Types**: [which types appeared: persona / episodic / instruction / skill_context]`;
-}

package/dist/memory/prompts/l3-persona.d.ts

@@ -1,6 +0,0 @@
-export declare const L3_PERSONA_SYSTEM_PROMPT = "You are a user profiling expert for a software engineering AI assistant.\n\nYour task is to synthesize a set of durable user memories (persona traits and instructions) into a concise, structured 4-layer Narrative Profile.\n\nRules:\n- Be STRICTLY grounded in the provided memories. Do NOT infer or fabricate traits.\n- If a trait appears only once and is ambiguous, omit it.\n- Prefer concrete observations over vague generalizations.\n- Instructions (hard rules the user gave) must be listed verbatim in \"Hard Rules\".\n- DEDUPLICATE Hard Rules: if multiple instruction memories express the same constraint (even with different wording), merge them into one canonical rule. Prefer the most specific and complete version.\n- Output ONLY the Markdown profile. No preamble.";
-export declare function formatL3PersonaPrompt(memories: Array<{
-    content: string;
-    type: string;
-    priority: number;
-}>): string;

package/dist/memory/prompts/l3-persona.js

@@ -1,60 +0,0 @@
-// ============================
-// L3 Persona Synthesis Prompt
-// ============================
-export const L3_PERSONA_SYSTEM_PROMPT = `You are a user profiling expert for a software engineering AI assistant.
-
-Your task is to synthesize a set of durable user memories (persona traits and instructions) into a concise, structured 4-layer Narrative Profile.
-
-Rules:
-- Be STRICTLY grounded in the provided memories. Do NOT infer or fabricate traits.
-- If a trait appears only once and is ambiguous, omit it.
-- Prefer concrete observations over vague generalizations.
-- Instructions (hard rules the user gave) must be listed verbatim in "Hard Rules".
-- DEDUPLICATE Hard Rules: if multiple instruction memories express the same constraint (even with different wording), merge them into one canonical rule. Prefer the most specific and complete version.
-- Output ONLY the Markdown profile. No preamble.`;
-export function formatL3PersonaPrompt(memories) {
-    const personaLines = memories
-        .filter(m => m.type === "persona")
-        .sort((a, b) => b.priority - a.priority)
-        .map(m => `- ${m.content}`)
-        .join("\n");
-    const instructionLines = memories
-        .filter(m => m.type === "instruction")
-        .sort((a, b) => b.priority - a.priority)
-        .map(m => `- ${m.content}`)
-        .join("\n");
-    return `Synthesize a structured Narrative Profile from the following user memories.
-
-### Persona Memories (stable traits, preferences):
-${personaLines || "- (none)"}
-
-### Instruction Memories (hard rules from the user):
-${instructionLines || "- (none)"}
-
-### Output Format (strict Markdown):
-## User Narrative Profile
-
-### Layer 1 — Base Anchors
-(Stable identity: role, years of experience, core domain, language preferences)
-- [anchor 1]
-- [anchor 2]
-
-### Layer 2 — Interest Graph
-(Topics they care about most: architecture, performance, DX, shipping speed, etc.)
-- [interest 1]
-- [interest 2]
-
-### Layer 3 — Skill Map  
-(Concrete tools, frameworks, languages, and patterns they use or prefer)
-- [skill/tool 1]
-- [skill/tool 2]
-
-### Layer 4 — Behavioural Patterns
-(Observable working styles: how they iterate, what they avoid, what they reward)
-- [pattern 1]
-- [pattern 2]
-
-### Hard Rules (must never be violated)
-- [verbatim instruction 1]
-- [verbatim instruction 2]`;
-}