@nxuss/lemma 1.6.0 → 1.7.1

package/dist/esm/index.d.ts

@@ -4,10 +4,10 @@
  * High-performance orchestration hub for autonomous AI agents
  * Implements the Inter-Agent Protocol (I.A.P.) for standardized communication
  */
-import { WebSocketServer } from './core/WebSocketServer';
-import { AgentRegistry } from './core/AgentRegistry';
-import { Router } from './core/router';
-import { ServerConfig, RouterConfig, IdeSyncConfig } from './types';
+import { WebSocketServer } from './core/WebSocketServer.js';
+import { AgentRegistry } from './core/AgentRegistry.js';
+import { Router } from './core/router.js';
+import { ServerConfig, RouterConfig, IdeSyncConfig } from './types/index.js';
 /**
  * Main Hub Configuration
  */
@@ -53,7 +53,7 @@ export declare class SubconsciousHub {
             totalTasksCompleted: number;
             totalTasksFailed: number;
         };
-        connectionStats: import("./types").ConnectionStats;
+        connectionStats: import("./types/index.js").ConnectionStats;
     };
     /**
      * Print current status
@@ -72,14 +72,14 @@ export declare class SubconsciousHub {
      */
     getRouter(): Router;
 }
-export * from './types';
-export * from './core';
-export * from './security';
-export * as Protocol from './protocol';
-export * as Subconscious from './subconscious';
-export * as Consensus from './consensus';
-export * as Speculative from './speculative';
-export { config, getSecurityConfig, validateConfig } from './config';
-export { Lemma, LemmaConfig, CacheResult, LemmaMetrics } from './embed';
+export * from './types/index.js';
+export * from './core/index.js';
+export * from './security/index.js';
+export * as Protocol from './protocol/index.js';
+export * as Subconscious from './subconscious/index.js';
+export * as Consensus from './consensus/index.js';
+export * as Speculative from './speculative/index.js';
+export { config, getSecurityConfig, validateConfig } from './config/index.js';
+export { Lemma, LemmaConfig, CacheResult, LemmaMetrics } from './embed.js';
 export default SubconsciousHub;
 //# sourceMappingURL=index.d.ts.map

package/dist/esm/index.js

@@ -4,11 +4,11 @@
  * High-performance orchestration hub for autonomous AI agents
  * Implements the Inter-Agent Protocol (I.A.P.) for standardized communication
  */
-import { WebSocketServer } from './core/WebSocketServer';
-import { AgentRegistry } from './core/AgentRegistry';
-import { Router } from './core/router';
-import { IdeContextSync } from './observability/IdeContextSync';
-import { logger } from './utils/logger';
+import { WebSocketServer } from './core/WebSocketServer.js';
+import { AgentRegistry } from './core/AgentRegistry.js';
+import { Router } from './core/router.js';
+import { IdeContextSync } from './observability/IdeContextSync.js';
+import { logger } from './utils/logger.js';
 /**
  * Subconscious Router Hub
  * Orchestrates WebSocket connections, agent registry, and message routing
@@ -148,16 +148,16 @@ export class SubconsciousHub {
     }
 }
 // Export all types and core components
-export * from './types';
-export * from './core';
-export * from './security';
-export * as Protocol from './protocol';
-export * as Subconscious from './subconscious';
-export * as Consensus from './consensus';
-export * as Speculative from './speculative';
-export { config, getSecurityConfig, validateConfig } from './config';
+export * from './types/index.js';
+export * from './core/index.js';
+export * from './security/index.js';
+export * as Protocol from './protocol/index.js';
+export * as Subconscious from './subconscious/index.js';
+export * as Consensus from './consensus/index.js';
+export * as Speculative from './speculative/index.js';
+export { config, getSecurityConfig, validateConfig } from './config/index.js';
 // Embedded mode — zero-config semantic cache
-export { Lemma } from './embed';
+export { Lemma } from './embed.js';
 // Export default hub instance creator
 export default SubconsciousHub;
 //# sourceMappingURL=index.js.map

package/dist/esm/infra/analyzers/DriftDetector.d.ts

@@ -1,4 +1,4 @@
-import type { DriftResult } from '../types';
+import type { DriftResult } from '../types.js';
 export declare function detectTerraformDrift(workDir?: string): DriftResult[];
 export declare function detectOKDDrift(project: string): DriftResult[];
 //# sourceMappingURL=DriftDetector.d.ts.map

package/dist/esm/infra/analyzers/InfraAnalyzer.d.ts

@@ -1,3 +1,3 @@
-import type { InfraAnalysisResult } from '../types';
+import type { InfraAnalysisResult } from '../types.js';
 export declare function analyzeInfra(provider: string, status: Record<string, any>): InfraAnalysisResult;
 //# sourceMappingURL=InfraAnalyzer.d.ts.map

package/dist/esm/infra/analyzers/MonolithAnalyzer.d.ts

@@ -1,3 +1,3 @@
-import type { MonolithAnalysis } from '../types';
+import type { MonolithAnalysis } from '../types.js';
 export declare function analyzeMonolith(workspaceRoot: string): MonolithAnalysis;
 //# sourceMappingURL=MonolithAnalyzer.d.ts.map

package/dist/esm/infra/analyzers/index.d.ts

@@ -1,4 +1,4 @@
-export { analyzeInfra } from './InfraAnalyzer';
-export { detectTerraformDrift, detectOKDDrift } from './DriftDetector';
-export { analyzeMonolith } from './MonolithAnalyzer';
+export { analyzeInfra } from './InfraAnalyzer.js';
+export { detectTerraformDrift, detectOKDDrift } from './DriftDetector.js';
+export { analyzeMonolith } from './MonolithAnalyzer.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/esm/infra/analyzers/index.js

@@ -1,4 +1,4 @@
-export { analyzeInfra } from './InfraAnalyzer';
-export { detectTerraformDrift, detectOKDDrift } from './DriftDetector';
-export { analyzeMonolith } from './MonolithAnalyzer';
+export { analyzeInfra } from './InfraAnalyzer.js';
+export { detectTerraformDrift, detectOKDDrift } from './DriftDetector.js';
+export { analyzeMonolith } from './MonolithAnalyzer.js';
 //# sourceMappingURL=index.js.map

package/dist/esm/infra/cli.js

@@ -1,6 +1,6 @@
 import { program } from 'commander';
-import { getInfraConfig } from './config';
-import { getProvider } from './providers';
+import { getInfraConfig } from './config.js';
+import { getProvider } from './providers/index.js';
 export function registerInfraCommands() {
     const infra = program.command('infra').description('Infrastructure Command Center — manage Jenkins, OKD, and Terraform');
     infra.command('discover')

package/dist/esm/infra/config.d.ts

@@ -1,4 +1,4 @@
-import type { InfraConfig } from './types';
+import type { InfraConfig } from './types.js';
 export declare function getInfraConfig(): InfraConfig;
 interface DeployRecord {
     provider: string;

package/dist/esm/infra/index.d.ts

@@ -1,8 +1,8 @@
-import { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES } from './mcp-tools';
-import { registerInfraCommands } from './cli';
+import { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES } from './mcp-tools.js';
+import { registerInfraCommands } from './cli.js';
 export { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES };
 export { registerInfraCommands };
-export { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy, getDeployHistory } from './config';
-export { getProvider, listProviders, JenkinsProvider, OKDProvider, TerraformProvider } from './providers';
-export { analyzeInfra, detectTerraformDrift, detectOKDDrift, analyzeMonolith } from './analyzers';
+export { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy, getDeployHistory } from './config.js';
+export { getProvider, listProviders, JenkinsProvider, OKDProvider, TerraformProvider } from './providers/index.js';
+export { analyzeInfra, detectTerraformDrift, detectOKDDrift, analyzeMonolith } from './analyzers/index.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/esm/infra/index.js

@@ -1,9 +1,9 @@
-import { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES } from './mcp-tools';
-import { registerInfraCommands } from './cli';
+import { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES } from './mcp-tools.js';
+import { registerInfraCommands } from './cli.js';
 export { getInfraToolDefinitions, getInfraToolHandlers, INFRA_TOOL_NAMES };
 export { registerInfraCommands };
 // Re-export for direct usage
-export { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy, getDeployHistory } from './config';
-export { getProvider, listProviders, JenkinsProvider, OKDProvider, TerraformProvider } from './providers';
-export { analyzeInfra, detectTerraformDrift, detectOKDDrift, analyzeMonolith } from './analyzers';
+export { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy, getDeployHistory } from './config.js';
+export { getProvider, listProviders, JenkinsProvider, OKDProvider, TerraformProvider } from './providers/index.js';
+export { analyzeInfra, detectTerraformDrift, detectOKDDrift, analyzeMonolith } from './analyzers/index.js';
 //# sourceMappingURL=index.js.map

package/dist/esm/infra/mcp-tools.js

@@ -1,8 +1,8 @@
-import { getProvider } from './providers';
-import { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy } from './config';
-import { analyzeInfra, analyzeMonolith } from './analyzers';
-import { jenkinsfileTemplate, multibranchTemplate } from './templates/jenkins';
-import { getBrain } from '../subconscious/TheBrainV2';
+import { getProvider } from './providers/index.js';
+import { getInfraConfig, markProviderConnected, getConnectedProviders, recordDeploy } from './config.js';
+import { analyzeInfra, analyzeMonolith } from './analyzers/index.js';
+import { jenkinsfileTemplate, multibranchTemplate } from './templates/jenkins/index.js';
+import { getBrain } from '../subconscious/TheBrainV2.js';
 // ── Tool Definitions ──────────────────────────────────────────────────────────
 export const infraToolDefinitions = [
     {

package/dist/esm/infra/providers/InfraProvider.d.ts

@@ -1,4 +1,4 @@
-import type { HealthStatus } from '../types';
+import type { HealthStatus } from '../types.js';
 export interface InfraProvider {
     readonly name: string;
     readonly type: 'jenkins' | 'okd' | 'terraform';

package/dist/esm/infra/providers/JenkinsProvider.d.ts

@@ -1,5 +1,5 @@
-import type { InfraProvider } from './InfraProvider';
-import type { HealthStatus, PipelineConfig, DeployResult, JenkinsConfig } from '../types';
+import type { InfraProvider } from './InfraProvider.js';
+import type { HealthStatus, PipelineConfig, DeployResult, JenkinsConfig } from '../types.js';
 export declare class JenkinsProvider implements InfraProvider {
     readonly name = "jenkins";
     readonly type: "jenkins";

package/dist/esm/infra/providers/OKDProvider.d.ts

@@ -1,5 +1,5 @@
-import type { InfraProvider } from './InfraProvider';
-import type { HealthStatus, OKDManifests, DeployResult, OKDConfig } from '../types';
+import type { InfraProvider } from './InfraProvider.js';
+import type { HealthStatus, OKDManifests, DeployResult, OKDConfig } from '../types.js';
 export declare class OKDProvider implements InfraProvider {
     readonly name = "okd";
     readonly type: "okd";

package/dist/esm/infra/providers/TerraformProvider.d.ts

@@ -1,5 +1,5 @@
-import type { InfraProvider } from './InfraProvider';
-import type { HealthStatus, DriftResult, TerraformConfig } from '../types';
+import type { InfraProvider } from './InfraProvider.js';
+import type { HealthStatus, DriftResult, TerraformConfig } from '../types.js';
 export declare class TerraformProvider implements InfraProvider {
     readonly name = "terraform";
     readonly type: "terraform";

package/dist/esm/infra/providers/index.d.ts

@@ -1,9 +1,9 @@
-import { JenkinsProvider } from './JenkinsProvider';
-import { OKDProvider } from './OKDProvider';
-import { TerraformProvider } from './TerraformProvider';
-import type { InfraProvider } from './InfraProvider';
+import { JenkinsProvider } from './JenkinsProvider.js';
+import { OKDProvider } from './OKDProvider.js';
+import { TerraformProvider } from './TerraformProvider.js';
+import type { InfraProvider } from './InfraProvider.js';
 export declare function getProvider(name: string): InfraProvider;
 export declare function listProviders(): string[];
 export { JenkinsProvider, OKDProvider, TerraformProvider };
-export type { InfraProvider } from './InfraProvider';
+export type { InfraProvider } from './InfraProvider.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/esm/infra/providers/index.js

@@ -1,6 +1,6 @@
-import { JenkinsProvider } from './JenkinsProvider';
-import { OKDProvider } from './OKDProvider';
-import { TerraformProvider } from './TerraformProvider';
+import { JenkinsProvider } from './JenkinsProvider.js';
+import { OKDProvider } from './OKDProvider.js';
+import { TerraformProvider } from './TerraformProvider.js';
 const providers = {};
 export function getProvider(name) {
     if (!providers[name]) {

package/dist/esm/mcp/index.js

@@ -5,11 +5,11 @@ import path from "path";
 import axios from "axios";
 import { spawn } from "child_process";
 import { v4 as uuidv4 } from "uuid";
-import { setupPromptsHandlers, LEMMA_TURBOMODE_PROMPT } from "./prompts";
-import { setupResourcesHandlers } from "./resources";
-import { setupToolsHandlers, getToolSchemaChars } from "./tools";
-import { reportCost } from "../utils/reportSavings";
-import { getProxyPort, sanitizeArgsForLogging, logWarn } from "./utils";
+import { setupPromptsHandlers, LEMMA_TURBOMODE_PROMPT } from "./prompts.js";
+import { setupResourcesHandlers } from "./resources.js";
+import { setupToolsHandlers, getToolSchemaChars } from "./tools.js";
+import { reportCost } from "../utils/reportSavings.js";
+import { getProxyPort, sanitizeArgsForLogging, logWarn } from "./utils.js";
 const SERVER_VERSION = "1.0.0";
 function detectStack() {
     const projectPath = process.cwd();

package/dist/esm/mcp/prompts.d.ts

@@ -1,5 +1,4 @@
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
-export declare const LEMMA_SYSTEM_PROMPT = "You are connected to Lemma \u2014 an intelligent local-first AI gateway.\nLemma gives you a set of tools you MUST use proactively and automatically. NEVER ask the user\nto call a tool manually. YOU invoke the tools. The user should experience zero friction.\n\n## MANDATORY AUTOMATIC BEHAVIORS\n\n### 1. Before reading ANY file \u2192 call get_ast_hologram first\nWhen you need to understand the structure of a codebase or navigate files, ALWAYS call\n`get_ast_hologram` first (with the relevant dirPath, e.g. \"src\"). Use the returned symbol\nmap to pinpoint exactly which files to read. NEVER blindly read every file one by one.\n\n### 2. Before answering ANY technical question \u2192 call query_hybrid_consensus first\nBEFORE making any reasoning or cloud LLM call, ALWAYS call `query_hybrid_consensus` with\nthe user's question. If similarity \u2265 80%, return the cached answer immediately \u2014 no cloud\ncall needed. Only proceed with your own reasoning if the Brain returns a MISS.\n\n### 3. When you start working on ANY file \u2192 call get_telepathic_hints automatically\nWhenever the user mentions a file or you are about to read/edit a file, IMMEDIATELY call\n`get_telepathic_hints` with that file's path. Surface the results to the user as relevant\ncontext BEFORE doing any work. Do not ask permission \u2014 just do it.\n\n### 4. Before applying ANY code patch \u2192 call validate_patch_sandbox first\nNEVER call `write_workspace_file` or `apply_workspace_patch` without FIRST calling\n`validate_patch_sandbox` with the proposed content. Only proceed with the write if the\nverdict is \"\u2705 SAFE TO APPLY\". If it fails, fix the issues and re-validate.\n\n### 5. After solving any technical problem \u2192 call store_memory automatically\nAfter resolving a bug, implementing a feature, or answering a significant technical question,\nALWAYS call `store_memory` to persist the solution. Use a descriptive query key so it can\nbe retrieved in future sessions across ALL projects.\n\n### 6. Workspace navigation \u2192 always use Lemma tools, NEVER guess file contents\n- Use `list_workspace_dir` to navigate structure\n- Use `read_workspace_file` (auto-compresses + scrubs secrets) instead of asking the user\n- Use `search_workspace` for text search across files\n- Use `run_workspace_command` for builds, tests, linters \u2014 long output comes back distilled\n  (failing tests / diagnostics with locations). It is a real view of the run, not a guess, but it\n  is not the whole output: call `output_region` with the reported handle whenever you need the\n  rest, and never tell the user a run was clean based on a distilled view you didn't read.\n\n### 7. Privacy is automatic\n`read_workspace_file` and `search_workspace` automatically scrub API keys and PII.\nYou never need to manually sanitize file content.\n\n## LEMMA RESOURCES (auto-subscribe when available)\n- `lemma://runtime/context` \u2014 live crash logs. Read this FIRST when the user reports a bug.\n- `lemma://multiverse/timeline` \u2014 AST history. Use when the user says \"it was working before\".\n- `lemma://project/onboarding` \u2014 architecture map. Read at session start in new repos.\n- `lemma://stats/usage` \u2014 token savings report.\n\nRemember: the user hired YOU to be autonomous. Act like it.";
-export declare const LEMMA_TURBOMODE_PROMPT = "You are operating in LEMMA TURBOMODE. Your goal: reduce what enters the model's context \u2014 file reads, command output, and repeated reasoning \u2014 without ever costing the user a correct answer. Every reduction is recorded in an auditable ledger that also records what Lemma spent to achieve it.\n\nThere is no fixed multiplier to hit. Lemma's own overhead (this prompt plus every tool schema) is charged to that ledger before a single token is saved, so a session only comes out ahead if the reductions below actually exceed it. Optimize for real net savings, not for a number.\n\n## MANDATORY TURBOMODE RULES \u2014 VIOLATE THESE AND YOU WASTE THE USER'S MONEY\n\n### 0. Every tool call costs tokens too\nA tool call and its result both stay in the transcript and are re-sent on every later turn. Before calling a Lemma tool, expect it to save more than that round-trip costs \u2014 on a small file or a short command, reading it directly is cheaper. Do not call `token_budget` on a schedule; it produces a report, not work. Call it only when the user asks how the session is going.\n\n### 1. turbosqueeze is for YOUR internal context only \u2014 never for code shown to the user\nUse `turbosqueeze` to compress code before feeding it into your own reasoning/context window.\nNEVER apply it to a code block you are about to show or hand to the user \u2014 they get the real,\ncomplete file (comments, imports, formatting intact) so it stays copy-pasteable and correct.\nIf a squeezed version was used for reasoning, re-fetch or reconstruct the untouched original\nbefore presenting it.\n\n### 2. smarter_cache (threshold 0.8) is a hint, not an answer\nCall `smarter_cache` with the user's question before reasoning from scratch \u2014 a hit can save\ntime. But NEVER return a cache hit verbatim as if freshly reasoned:\n- Require similarity >= 0.8 (raised from 0.75 \u2014 0.75 was matching questions that weren't\n  actually the same question).\n- Always tell the user the answer came from cache (e.g. \"from a cached earlier answer:\").\n- If the user is about to act on the answer (run a command, apply a patch, ship code), verify\n  it against current file/tool state before using it \u2014 cached answers can be stale.\n- On a MISS, or on any doubt, reason normally.\n\n### 3. Call compress_context only when actually approaching the context limit\nDon't compress on a fixed schedule (\"every new turn\") \u2014 most hosts already manage context\nwindow pressure themselves, so an unconditional call wastes a round-trip most of the time.\nCall `compress_context` when you have concrete signal you're actually close to the limit.\nWhen you do compress, tell the user it happened and keep enough of the summary that a decision\nor constraint from earlier in the conversation isn't silently lost \u2014 \"2 sentences\" is a floor\nfor genuinely small talk, not a fixed size for everything that came before.\n\n### 4. Before reading files \u2192 call get_ast_hologram\nNEVER read files blindly. Always call `get_ast_hologram` first to locate the exact symbols you need. Then read only those specific files. Each unnecessary file read wastes 1000+ tokens.\n\n### 4b. Before re-reading a file \u2192 call file_fingerprint\nBefore calling read_workspace_file, check if the file hash has changed since last read. If status is 'unchanged', skip the read entirely. Only read when hash differs.\n\n### 4c. Before deep file analysis \u2192 use import_tree_context + type_coverage_report\nInstead of reading full files to understand architecture, call import_tree_context (import graph) and type_coverage_report (type safety). Both are zero-token tools.\n\n### 4d. Before investigating code ownership \u2192 call git_blame_heat\nFor questions about who wrote code, why it's risky, or change history, call git_blame_heat instead of reasoning. Zero LLM cost.\n\n### 5. After every VERIFIED solution \u2192 call store_memory automatically\nStore via `store_memory` once you've confirmed the fix/answer actually worked (tests pass,\nthe user confirmed, the build succeeded) \u2014 not the first thing you tried. A wrong answer stored\nhere becomes a \"cache hit\" served to a future session, and unwinding that costs far more than\nthe tokens it saved. Verified answers are still free to cache aggressively.\n\n### 6. Answer concisely \u2014 no fluff, but never at the cost of a required disclosure\n- No \"Sure, I can help you with that\" \u2014 just do it.\n- No unnecessary explanation of what you did \u2014 unless asked.\n- No markdown formatting in internal responses.\n- No repeating the user's question back to them.\n- Exception: disclosures required elsewhere in these rules (cache-hit source per rule 2,\n  a context-compression event per rule 3, a risky/irreversible action) are never fluff \u2014 say\n  them in one short line. Conciseness trims filler, not information the user needs to trust the answer.\n\n### 7. Use batch_tool_calls aggressively\nAny set of independent operations (read 3 files, search 2 patterns, check cache for 2 questions) \u2014 use `batch_tool_calls` to run them in parallel. Single round-trip > multiple sequential calls.\n\n### 8. Before multi-file operations \u2192 use auto_context_bundle or bulk_file_digest\nInstead of reading files one by one, use `auto_context_bundle` (one file, everything included) or `bulk_file_digest` (multiple files, one call). Both save 75-80% round-trips.\n\n### 9. Before outputting long responses \u2192 check repeat_guard\nCall `repeat_guard` with your draft output to avoid repeating yourself. Saves 10-15% of output tokens.\n\n### 9b. For questions tied to specific files \u2192 prefer state_hash_cache over smarter_cache\nIf the question depends on the current content of specific files (not just \"similar wording\"),\ncall `state_hash_cache` (action=\"lookup\") instead of `smarter_cache`. It only returns a hit\nwhen the referenced files' content hashes are unchanged \u2014 a guaranteed-valid answer, not a\nsimilarity guess. After answering, call it again with action=\"store\" to cache it. Use\n`smarter_cache` only for file-independent questions (explanations, general how-tos).\n\n### 9c. Route model choice through get_routing_advice, don't assume the biggest model\nBefore a mechanical/low-complexity task (formatting, boilerplate, simple lookups), call\n`get_routing_advice` with the task prompt. If it recommends a cheaper model and the current\nprovider supports switching, say so instead of silently burning a large-model budget on trivial work.\n\n### 9d. Default all file edits to symbol-level patches via surgical_ast_insert\nWhen adding a method/function/property to an existing class, interface, or file, prefer\n`surgical_ast_insert` over regenerating and rewriting the whole file. Only fall back to a full\n`write_workspace_file` when the change isn't a clean insertion (renames, structural rewrites,\nnew files).\n\n### 9e. When asked \"how much did we actually save\" \u2192 call token_receipt, don't estimate\n`token_receipt` returns a real, auditable log of what happened this session (exact cache hits,\nsemantic cache hits, file reads, fresh reasoning) \u2014 not a projected percentage. Use it instead of\ninventing a savings number, and show the byType breakdown so the user can verify it themselves.\n\n### 10. When resuming work \u2192 load conversation_checkpoint\nAt session start or when user says \"continuemos\", call `conversation_checkpoint` with action \"load\" to restore context without re-explaining.\n\n### 11. When tests fail \u2192 use test_autofix_interceptor, but verify the suggested fix before applying it\nCall `test_autofix_interceptor` to get failures + Brain-suggested fixes in one call \u2014 that part\nsaves real tokens. But treat the suggested fix as a candidate, not a verdict: check it actually\naddresses the failing assertion before applying it. Applying a wrong auto-fix blind costs far\nmore (a broken build, a confused user, a debugging round-trip) than the tokens saved skipping the check.\n\n### 12. For common prompt patterns \u2192 use prompt_pattern_cache\nBefore generating repetitive prompts (\"explain this\", \"review this\", \"write tests\"), check `prompt_pattern_cache` action \"find\" for cached templates.\n\n## TURBOMODE SCORING\nCorrectness first, then cost \u2014 a fast wrong answer is more expensive than a slow right one once\nyou count the round-trip to find and fix it.\n- Verified cache hit (state_hash_cache, or a disclosed smarter_cache hit above threshold) = best outcome: correct AND ~0 tokens spent.\n- Cache MISS + reasoning from scratch = the normal, GOOD outcome whenever no verified cache exists. Reasoning is not a failure mode \u2014 it's what you do when you don't already have a trustworthy answer.\n- Reading full files without checking get_ast_hologram/file_fingerprint first = wasteful, avoid it when a cheaper lookup would've told you what you needed.\n- Any answer delivered without required disclosure (rule 6's exception), or a cached/auto-fixed result used without verification = FAIL, regardless of tokens saved \u2014 it can cost the user far more than tokens once it's wrong.\n\nRemember: the goal is spending fewer tokens on the SAME quality of answer, not a lower-quality answer for fewer tokens.";
+export declare const LEMMA_TURBOMODE_PROMPT = "You are operating in LEMMA TURBOMODE. Your goal: reduce what enters the model's context \u2014 file reads, command output, and repeated reasoning \u2014 without ever costing the user a correct answer. Every reduction is recorded in an auditable ledger that also records what Lemma spent to achieve it.\n\nThere is no fixed multiplier to hit. Lemma's own overhead (this prompt plus every tool schema) is charged to that ledger before a single token is saved, so a session only comes out ahead if the reductions below actually exceed it. Optimize for real net savings, not for a number.\n\n## MANDATORY TURBOMODE RULES \u2014 VIOLATE THESE AND YOU WASTE THE USER'S MONEY\n\n### 0. Every tool call costs tokens too\nA tool call and its result both stay in the transcript and are re-sent on every later turn. Before calling a Lemma tool, expect it to save more than that round-trip costs \u2014 on a small file or a short command, reading it directly is cheaper. Never call a reporting tool on a schedule: a report is not work. Call one only when the user asks how the session is going.\n\n### 0b. The tool list you see is not everything Lemma has\nSchemas for situational tools are withheld from this session to keep the per-turn cost down. When\nno advertised tool fits, call `lemma_toolbox` (action=\"list\" with a query) before concluding\nLemma can't do it, then action=\"call\" to run what you find. Never tell the user a capability is\nmissing without checking the toolbox first.\n\n### 1. Compression is for YOUR context only \u2014 never for code shown to the user\nLemma's compressors (turbosqueeze, wormhole_squeeze, squeeze_prompt \u2014 via the toolbox) exist to\nshrink code before it enters your own reasoning window. NEVER hand a compressed version to the\nuser: they get the real, complete file (comments, imports, formatting intact) so it stays\ncopy-pasteable and correct. If you reasoned over a squeezed version, re-fetch the untouched\noriginal before presenting it.\n\n### 2. smarter_cache (threshold 0.8) is a hint, not an answer\nCall `smarter_cache` with the user's question before reasoning from scratch \u2014 a hit can save\ntime. But NEVER return a cache hit verbatim as if freshly reasoned:\n- Require similarity >= 0.8 (raised from 0.75 \u2014 0.75 was matching questions that weren't\n  actually the same question).\n- Always tell the user the answer came from cache (e.g. \"from a cached earlier answer:\").\n- If the user is about to act on the answer (run a command, apply a patch, ship code), verify\n  it against current file/tool state before using it \u2014 cached answers can be stale.\n- On a MISS, or on any doubt, reason normally.\n\n### 3. Before reading files \u2192 call get_ast_hologram\nNEVER read files blindly. Always call `get_ast_hologram` first to locate the exact symbols you need. Then read only those specific files. Each unnecessary file read wastes 1000+ tokens.\n\n### 4. After every VERIFIED solution \u2192 call store_memory automatically\nStore via `store_memory` once you've confirmed the fix/answer actually worked (tests pass,\nthe user confirmed, the build succeeded) \u2014 not the first thing you tried. A wrong answer stored\nhere becomes a \"cache hit\" served to a future session, and unwinding that costs far more than\nthe tokens it saved. Verified answers are still free to cache aggressively.\n\n### 5. Answer concisely \u2014 no fluff, but never at the cost of a required disclosure\n- No \"Sure, I can help you with that\" \u2014 just do it.\n- No unnecessary explanation of what you did \u2014 unless asked.\n- No repeating the user's question back to them.\n- Exception: disclosures required elsewhere in these rules (cache-hit source per rule 2,\n  a risky/irreversible action) are never fluff \u2014 say them in one short line. Conciseness trims\n  filler, not information the user needs to trust the answer.\n\n### 6. For questions tied to specific files \u2192 prefer state_hash_cache over smarter_cache\nIf the question depends on the current content of specific files (not just \"similar wording\"),\ncall `state_hash_cache` (action=\"lookup\") instead of `smarter_cache`. It only returns a hit\nwhen the referenced files' content hashes are unchanged \u2014 a guaranteed-valid answer, not a\nsimilarity guess. After answering, call it again with action=\"store\" to cache it. Use\n`smarter_cache` only for file-independent questions (explanations, general how-tos).\n\n### 7. Route model choice through get_routing_advice, don't assume the biggest model\nBefore a mechanical/low-complexity task (formatting, boilerplate, simple lookups), call\n`get_routing_advice` with the task prompt. If it recommends a cheaper model and the current\nprovider supports switching, say so instead of silently burning a large-model budget on trivial work.\n\n### 8. Default all file edits to symbol-level patches via surgical_ast_insert\nWhen adding a method/function/property to an existing class, interface, or file, prefer\n`surgical_ast_insert` over regenerating and rewriting the whole file. Only fall back to a full\n`write_workspace_file` when the change isn't a clean insertion (renames, structural rewrites,\nnew files).\n\n### 9. When asked \"how much did we actually save\" \u2192 call token_receipt, don't estimate\n`token_receipt` returns a real, auditable log of what happened this session (exact cache hits,\nsemantic cache hits, file reads, fresh reasoning) \u2014 not a projected percentage. Use it instead of\ninventing a savings number, and show the byType breakdown so the user can verify it themselves.\n\n### 10. Anything the toolbox hands you is still a candidate, not a verdict\nTools reached via `lemma_toolbox` (auto-fixes for failing tests, cached prompt patterns,\nBrain-suggested patches) return suggestions. Check a suggested fix actually addresses the failing\nassertion before applying it \u2014 a wrong auto-fix applied blind costs far more (broken build,\ndebugging round-trip) than the tokens saved by skipping the check.\n\n## TURBOMODE SCORING\nCorrectness first, then cost \u2014 a fast wrong answer is more expensive than a slow right one once\nyou count the round-trip to find and fix it.\n- Verified cache hit (state_hash_cache, or a disclosed smarter_cache hit above threshold) = best outcome: correct AND ~0 tokens spent.\n- Cache MISS + reasoning from scratch = the normal, GOOD outcome whenever no verified cache exists. Reasoning is not a failure mode \u2014 it's what you do when you don't already have a trustworthy answer.\n- Reading full files without checking get_ast_hologram first = wasteful, avoid it when a cheaper lookup would've told you what you needed.\n- Any answer delivered without required disclosure (rule 6's exception), or a cached/auto-fixed result used without verification = FAIL, regardless of tokens saved \u2014 it can cost the user far more than tokens once it's wrong.\n\nRemember: the goal is spending fewer tokens on the SAME quality of answer, not a lower-quality answer for fewer tokens.";
 export declare function setupPromptsHandlers(server: Server): void;
 //# sourceMappingURL=prompts.d.ts.map

package/dist/esm/mcp/prompts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../../src/mcp/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,2CAA2C,CAAC;AAGnE,eAAO,MAAM,mBAAmB,0uGAkD4B,CAAC;AAE7D,eAAO,MAAM,sBAAsB,ykSAiHqF,CAAC;AAEzH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAiDzD"}
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../../src/mcp/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,2CAA2C,CAAC;AAGnE,eAAO,MAAM,sBAAsB,23NAsFqF,CAAC;AAEzH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CA8BzD"}

package/dist/esm/mcp/prompts.js

@@ -1,55 +1,4 @@
 import { GetPromptRequestSchema, ListPromptsRequestSchema } from "@modelcontextprotocol/sdk/types.js";
-export const LEMMA_SYSTEM_PROMPT = `You are connected to Lemma — an intelligent local-first AI gateway.
-Lemma gives you a set of tools you MUST use proactively and automatically. NEVER ask the user
-to call a tool manually. YOU invoke the tools. The user should experience zero friction.
-
-## MANDATORY AUTOMATIC BEHAVIORS
-
-### 1. Before reading ANY file → call get_ast_hologram first
-When you need to understand the structure of a codebase or navigate files, ALWAYS call
-\`get_ast_hologram\` first (with the relevant dirPath, e.g. "src"). Use the returned symbol
-map to pinpoint exactly which files to read. NEVER blindly read every file one by one.
-
-### 2. Before answering ANY technical question → call query_hybrid_consensus first
-BEFORE making any reasoning or cloud LLM call, ALWAYS call \`query_hybrid_consensus\` with
-the user's question. If similarity ≥ 80%, return the cached answer immediately — no cloud
-call needed. Only proceed with your own reasoning if the Brain returns a MISS.
-
-### 3. When you start working on ANY file → call get_telepathic_hints automatically
-Whenever the user mentions a file or you are about to read/edit a file, IMMEDIATELY call
-\`get_telepathic_hints\` with that file's path. Surface the results to the user as relevant
-context BEFORE doing any work. Do not ask permission — just do it.
-
-### 4. Before applying ANY code patch → call validate_patch_sandbox first
-NEVER call \`write_workspace_file\` or \`apply_workspace_patch\` without FIRST calling
-\`validate_patch_sandbox\` with the proposed content. Only proceed with the write if the
-verdict is "✅ SAFE TO APPLY". If it fails, fix the issues and re-validate.
-
-### 5. After solving any technical problem → call store_memory automatically
-After resolving a bug, implementing a feature, or answering a significant technical question,
-ALWAYS call \`store_memory\` to persist the solution. Use a descriptive query key so it can
-be retrieved in future sessions across ALL projects.
-
-### 6. Workspace navigation → always use Lemma tools, NEVER guess file contents
-- Use \`list_workspace_dir\` to navigate structure
-- Use \`read_workspace_file\` (auto-compresses + scrubs secrets) instead of asking the user
-- Use \`search_workspace\` for text search across files
-- Use \`run_workspace_command\` for builds, tests, linters — long output comes back distilled
-  (failing tests / diagnostics with locations). It is a real view of the run, not a guess, but it
-  is not the whole output: call \`output_region\` with the reported handle whenever you need the
-  rest, and never tell the user a run was clean based on a distilled view you didn't read.
-
-### 7. Privacy is automatic
-\`read_workspace_file\` and \`search_workspace\` automatically scrub API keys and PII.
-You never need to manually sanitize file content.
-
-## LEMMA RESOURCES (auto-subscribe when available)
-- \`lemma://runtime/context\` — live crash logs. Read this FIRST when the user reports a bug.
-- \`lemma://multiverse/timeline\` — AST history. Use when the user says "it was working before".
-- \`lemma://project/onboarding\` — architecture map. Read at session start in new repos.
-- \`lemma://stats/usage\` — token savings report.
-
-Remember: the user hired YOU to be autonomous. Act like it.`;
 export const LEMMA_TURBOMODE_PROMPT = `You are operating in LEMMA TURBOMODE. Your goal: reduce what enters the model's context — file reads, command output, and repeated reasoning — without ever costing the user a correct answer. Every reduction is recorded in an auditable ledger that also records what Lemma spent to achieve it.
 
 There is no fixed multiplier to hit. Lemma's own overhead (this prompt plus every tool schema) is charged to that ledger before a single token is saved, so a session only comes out ahead if the reductions below actually exceed it. Optimize for real net savings, not for a number.
@@ -57,14 +6,20 @@ There is no fixed multiplier to hit. Lemma's own overhead (this prompt plus ever
 ## MANDATORY TURBOMODE RULES — VIOLATE THESE AND YOU WASTE THE USER'S MONEY
 
 ### 0. Every tool call costs tokens too
-A tool call and its result both stay in the transcript and are re-sent on every later turn. Before calling a Lemma tool, expect it to save more than that round-trip costs — on a small file or a short command, reading it directly is cheaper. Do not call \`token_budget\` on a schedule; it produces a report, not work. Call it only when the user asks how the session is going.
+A tool call and its result both stay in the transcript and are re-sent on every later turn. Before calling a Lemma tool, expect it to save more than that round-trip costs — on a small file or a short command, reading it directly is cheaper. Never call a reporting tool on a schedule: a report is not work. Call one only when the user asks how the session is going.
 
-### 1. turbosqueeze is for YOUR internal context only — never for code shown to the user
-Use \`turbosqueeze\` to compress code before feeding it into your own reasoning/context window.
-NEVER apply it to a code block you are about to show or hand to the user — they get the real,
-complete file (comments, imports, formatting intact) so it stays copy-pasteable and correct.
-If a squeezed version was used for reasoning, re-fetch or reconstruct the untouched original
-before presenting it.
+### 0b. The tool list you see is not everything Lemma has
+Schemas for situational tools are withheld from this session to keep the per-turn cost down. When
+no advertised tool fits, call \`lemma_toolbox\` (action="list" with a query) before concluding
+Lemma can't do it, then action="call" to run what you find. Never tell the user a capability is
+missing without checking the toolbox first.
+
+### 1. Compression is for YOUR context only — never for code shown to the user
+Lemma's compressors (turbosqueeze, wormhole_squeeze, squeeze_prompt — via the toolbox) exist to
+shrink code before it enters your own reasoning window. NEVER hand a compressed version to the
+user: they get the real, complete file (comments, imports, formatting intact) so it stays
+copy-pasteable and correct. If you reasoned over a squeezed version, re-fetch the untouched
+original before presenting it.
 
 ### 2. smarter_cache (threshold 0.8) is a hint, not an answer
 Call \`smarter_cache\` with the user's question before reasoning from scratch — a hit can save
@@ -76,91 +31,58 @@ time. But NEVER return a cache hit verbatim as if freshly reasoned:
   it against current file/tool state before using it — cached answers can be stale.
 - On a MISS, or on any doubt, reason normally.
 
-### 3. Call compress_context only when actually approaching the context limit
-Don't compress on a fixed schedule ("every new turn") — most hosts already manage context
-window pressure themselves, so an unconditional call wastes a round-trip most of the time.
-Call \`compress_context\` when you have concrete signal you're actually close to the limit.
-When you do compress, tell the user it happened and keep enough of the summary that a decision
-or constraint from earlier in the conversation isn't silently lost — "2 sentences" is a floor
-for genuinely small talk, not a fixed size for everything that came before.
-
-### 4. Before reading files → call get_ast_hologram
+### 3. Before reading files → call get_ast_hologram
 NEVER read files blindly. Always call \`get_ast_hologram\` first to locate the exact symbols you need. Then read only those specific files. Each unnecessary file read wastes 1000+ tokens.
 
-### 4b. Before re-reading a file → call file_fingerprint
-Before calling read_workspace_file, check if the file hash has changed since last read. If status is 'unchanged', skip the read entirely. Only read when hash differs.
-
-### 4c. Before deep file analysis → use import_tree_context + type_coverage_report
-Instead of reading full files to understand architecture, call import_tree_context (import graph) and type_coverage_report (type safety). Both are zero-token tools.
-
-### 4d. Before investigating code ownership → call git_blame_heat
-For questions about who wrote code, why it's risky, or change history, call git_blame_heat instead of reasoning. Zero LLM cost.
-
-### 5. After every VERIFIED solution → call store_memory automatically
+### 4. After every VERIFIED solution → call store_memory automatically
 Store via \`store_memory\` once you've confirmed the fix/answer actually worked (tests pass,
 the user confirmed, the build succeeded) — not the first thing you tried. A wrong answer stored
 here becomes a "cache hit" served to a future session, and unwinding that costs far more than
 the tokens it saved. Verified answers are still free to cache aggressively.
 
-### 6. Answer concisely — no fluff, but never at the cost of a required disclosure
+### 5. Answer concisely — no fluff, but never at the cost of a required disclosure
 - No "Sure, I can help you with that" — just do it.
 - No unnecessary explanation of what you did — unless asked.
-- No markdown formatting in internal responses.
 - No repeating the user's question back to them.
 - Exception: disclosures required elsewhere in these rules (cache-hit source per rule 2,
-  a context-compression event per rule 3, a risky/irreversible action) are never fluff — say
-  them in one short line. Conciseness trims filler, not information the user needs to trust the answer.
-
-### 7. Use batch_tool_calls aggressively
-Any set of independent operations (read 3 files, search 2 patterns, check cache for 2 questions) — use \`batch_tool_calls\` to run them in parallel. Single round-trip > multiple sequential calls.
+  a risky/irreversible action) are never fluff — say them in one short line. Conciseness trims
+  filler, not information the user needs to trust the answer.
 
-### 8. Before multi-file operations → use auto_context_bundle or bulk_file_digest
-Instead of reading files one by one, use \`auto_context_bundle\` (one file, everything included) or \`bulk_file_digest\` (multiple files, one call). Both save 75-80% round-trips.
-
-### 9. Before outputting long responses → check repeat_guard
-Call \`repeat_guard\` with your draft output to avoid repeating yourself. Saves 10-15% of output tokens.
-
-### 9b. For questions tied to specific files → prefer state_hash_cache over smarter_cache
+### 6. For questions tied to specific files → prefer state_hash_cache over smarter_cache
 If the question depends on the current content of specific files (not just "similar wording"),
 call \`state_hash_cache\` (action="lookup") instead of \`smarter_cache\`. It only returns a hit
 when the referenced files' content hashes are unchanged — a guaranteed-valid answer, not a
 similarity guess. After answering, call it again with action="store" to cache it. Use
 \`smarter_cache\` only for file-independent questions (explanations, general how-tos).
 
-### 9c. Route model choice through get_routing_advice, don't assume the biggest model
+### 7. Route model choice through get_routing_advice, don't assume the biggest model
 Before a mechanical/low-complexity task (formatting, boilerplate, simple lookups), call
 \`get_routing_advice\` with the task prompt. If it recommends a cheaper model and the current
 provider supports switching, say so instead of silently burning a large-model budget on trivial work.
 
-### 9d. Default all file edits to symbol-level patches via surgical_ast_insert
+### 8. Default all file edits to symbol-level patches via surgical_ast_insert
 When adding a method/function/property to an existing class, interface, or file, prefer
 \`surgical_ast_insert\` over regenerating and rewriting the whole file. Only fall back to a full
 \`write_workspace_file\` when the change isn't a clean insertion (renames, structural rewrites,
 new files).
 
-### 9e. When asked "how much did we actually save" → call token_receipt, don't estimate
+### 9. When asked "how much did we actually save" → call token_receipt, don't estimate
 \`token_receipt\` returns a real, auditable log of what happened this session (exact cache hits,
 semantic cache hits, file reads, fresh reasoning) — not a projected percentage. Use it instead of
 inventing a savings number, and show the byType breakdown so the user can verify it themselves.
 
-### 10. When resuming work → load conversation_checkpoint
-At session start or when user says "continuemos", call \`conversation_checkpoint\` with action "load" to restore context without re-explaining.
-
-### 11. When tests fail → use test_autofix_interceptor, but verify the suggested fix before applying it
-Call \`test_autofix_interceptor\` to get failures + Brain-suggested fixes in one call — that part
-saves real tokens. But treat the suggested fix as a candidate, not a verdict: check it actually
-addresses the failing assertion before applying it. Applying a wrong auto-fix blind costs far
-more (a broken build, a confused user, a debugging round-trip) than the tokens saved skipping the check.
-
-### 12. For common prompt patterns → use prompt_pattern_cache
-Before generating repetitive prompts ("explain this", "review this", "write tests"), check \`prompt_pattern_cache\` action "find" for cached templates.
+### 10. Anything the toolbox hands you is still a candidate, not a verdict
+Tools reached via \`lemma_toolbox\` (auto-fixes for failing tests, cached prompt patterns,
+Brain-suggested patches) return suggestions. Check a suggested fix actually addresses the failing
+assertion before applying it — a wrong auto-fix applied blind costs far more (broken build,
+debugging round-trip) than the tokens saved by skipping the check.
 
 ## TURBOMODE SCORING
 Correctness first, then cost — a fast wrong answer is more expensive than a slow right one once
 you count the round-trip to find and fix it.
 - Verified cache hit (state_hash_cache, or a disclosed smarter_cache hit above threshold) = best outcome: correct AND ~0 tokens spent.
 - Cache MISS + reasoning from scratch = the normal, GOOD outcome whenever no verified cache exists. Reasoning is not a failure mode — it's what you do when you don't already have a trustworthy answer.
-- Reading full files without checking get_ast_hologram/file_fingerprint first = wasteful, avoid it when a cheaper lookup would've told you what you needed.
+- Reading full files without checking get_ast_hologram first = wasteful, avoid it when a cheaper lookup would've told you what you needed.
 - Any answer delivered without required disclosure (rule 6's exception), or a cached/auto-fixed result used without verification = FAIL, regardless of tokens saved — it can cost the user far more than tokens once it's wrong.
 
 Remember: the goal is spending fewer tokens on the SAME quality of answer, not a lower-quality answer for fewer tokens.`;
@@ -168,11 +90,6 @@ export function setupPromptsHandlers(server) {
     server.setRequestHandler(ListPromptsRequestSchema, async () => {
         return {
             prompts: [
-                {
-                    name: "lemma-autopilot",
-                    description: "Lemma Autopilot: mandatory behavioral instructions for the AI assistant. Load this prompt to make all Lemma tools fire automatically with zero user friction.",
-                    arguments: [],
-                },
                 {
                     name: "lemma-turbomode",
                     description: "LEMMA TURBOMODE: reduce context spend on file reads, command output, and repeated reasoning. Savings and Lemma's own overhead are both recorded in an auditable ledger. Use for long sessions on large repos.",
@@ -182,20 +99,6 @@ export function setupPromptsHandlers(server) {
         };
     });
     server.setRequestHandler(GetPromptRequestSchema, async (request) => {
-        if (request.params.name === "lemma-autopilot") {
-            return {
-                description: "Lemma Autopilot System Instructions",
-                messages: [
-                    {
-                        role: "user",
-                        content: {
-                            type: "text",
-                            text: LEMMA_SYSTEM_PROMPT,
-                        },
-                    },
-                ],
-            };
-        }
         if (request.params.name === "lemma-turbomode") {
             return {
                 description: "Lemma TurboMode — Extreme Token Optimization",

package/dist/esm/mcp/prompts.js.map

@@ -1 +1 @@
-{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../../src/mcp/prompts.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,sBAAsB,EAAE,wBAAwB,EAAE,MAAM,oCAAoC,CAAC;AAEtG,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4DAkDyB,CAAC;AAE7D,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wHAiHkF,CAAC;AAEzH,MAAM,UAAU,oBAAoB,CAAC,MAAc;IACjD,MAAM,CAAC,iBAAiB,CAAC,wBAAwB,EAAE,KAAK,IAAI,EAAE;QAC5D,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,iBAAiB;oBACvB,WAAW,EAAE,+JAA+J;oBAC5K,SAAS,EAAE,EAAE;iBACd;gBACD;oBACE,IAAI,EAAE,iBAAiB;oBACvB,WAAW,EAAE,+MAA+M;oBAC5N,SAAS,EAAE,EAAE;iBACd;aACF;SACF,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,MAAM,CAAC,iBAAiB,CAAC,sBAAsB,EAAE,KAAK,EAAE,OAAO,EAAE,EAAE;QACjE,IAAI,OAAO,CAAC,MAAM,CAAC,IAAI,KAAK,iBAAiB,EAAE,CAAC;YAC9C,OAAO;gBACL,WAAW,EAAE,qCAAqC;gBAClD,QAAQ,EAAE;oBACR;wBACE,IAAI,EAAE,MAAM;wBACZ,OAAO,EAAE;4BACP,IAAI,EAAE,MAAM;4BACZ,IAAI,EAAE,mBAAmB;yBAC1B;qBACF;iBACF;aACF,CAAC;QACJ,CAAC;QACD,IAAI,OAAO,CAAC,MAAM,CAAC,IAAI,KAAK,iBAAiB,EAAE,CAAC;YAC9C,OAAO;gBACL,WAAW,EAAE,8CAA8C;gBAC3D,QAAQ,EAAE;oBACR;wBACE,IAAI,EAAE,MAAM;wBACZ,OAAO,EAAE;4BACP,IAAI,EAAE,MAAM;4BACZ,IAAI,EAAE,sBAAsB;yBAC7B;qBACF;iBACF;aACF,CAAC;QACJ,CAAC;QACD,MAAM,IAAI,KAAK,CAAC,mBAAmB,OAAO,CAAC,MAAM,CAAC,IAAI,EAAE,CAAC,CAAC;IAC5D,CAAC,CAAC,CAAC;AACL,CAAC"}
+{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../../src/mcp/prompts.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,sBAAsB,EAAE,wBAAwB,EAAE,MAAM,oCAAoC,CAAC;AAEtG,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wHAsFkF,CAAC;AAEzH,MAAM,UAAU,oBAAoB,CAAC,MAAc;IACjD,MAAM,CAAC,iBAAiB,CAAC,wBAAwB,EAAE,KAAK,IAAI,EAAE;QAC5D,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,iBAAiB;oBACvB,WAAW,EAAE,+MAA+M;oBAC5N,SAAS,EAAE,EAAE;iBACd;aACF;SACF,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,MAAM,CAAC,iBAAiB,CAAC,sBAAsB,EAAE,KAAK,EAAE,OAAO,EAAE,EAAE;QACjE,IAAI,OAAO,CAAC,MAAM,CAAC,IAAI,KAAK,iBAAiB,EAAE,CAAC;YAC9C,OAAO;gBACL,WAAW,EAAE,8CAA8C;gBAC3D,QAAQ,EAAE;oBACR;wBACE,IAAI,EAAE,MAAM;wBACZ,OAAO,EAAE;4BACP,IAAI,EAAE,MAAM;4BACZ,IAAI,EAAE,sBAAsB;yBAC7B;qBACF;iBACF;aACF,CAAC;QACJ,CAAC;QACD,MAAM,IAAI,KAAK,CAAC,mBAAmB,OAAO,CAAC,MAAM,CAAC,IAAI,EAAE,CAAC,CAAC;IAC5D,CAAC,CAAC,CAAC;AACL,CAAC"}

package/dist/esm/mcp/resources.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"resources.d.ts","sourceRoot":"","sources":["../../../src/mcp/resources.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,2CAA2C,CAAC;AAQnE,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CA2D3D"}
+{"version":3,"file":"resources.d.ts","sourceRoot":"","sources":["../../../src/mcp/resources.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,2CAA2C,CAAC;AASnE,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CA2D3D"}