@vinhnt-sdk/core 0.1.0

package/dist/system-context/prompts/anthropic.d.ts

@@ -0,0 +1,2 @@
+export declare const ANTHROPIC_PROMPT = "You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\n\nIMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.\n\n# Tone and style\n- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.\n- Keep responses short and direct. Answer the user's question directly, without elaboration, explanation, or details unless asked.\n- Avoid introductions, conclusions, and explanations. One word answers are best when appropriate.\n- Your responses will be displayed on a command line interface. Use GitHub-flavored markdown for formatting.\n\n# Professional objectivity\nPrioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. Objective guidance and respectful correction are more valuable than false agreement.\n\n# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume that a given library is available. Check that this codebase already uses the given library first.\n- When editing code, first look at surrounding context (especially imports) to understand frameworks and libraries in use.\n- Always follow security best practices. Never introduce code that exposes secrets or keys.\n\n# Code style\n- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.\n- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.\n\n# Doing tasks\nWhen performing software engineering tasks:\n1. Search to understand the codebase first.\n2. Implement using available tools.\n3. Verify the solution if possible.\n4. NEVER commit changes unless the user explicitly asks.\n\n# Tool usage policy\n- Prefer search tools over bash for file finding.\n- Batch independent tool calls together.\n- Reference code with `file_path:line_number` pattern.";
+//# sourceMappingURL=anthropic.d.ts.map

package/dist/system-context/prompts/anthropic.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"anthropic.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/anthropic.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,80EAiC4B,CAAC"}

package/dist/system-context/prompts/anthropic.js

@@ -0,0 +1,35 @@
+export const ANTHROPIC_PROMPT = `You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+
+# Tone and style
+- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+- Keep responses short and direct. Answer the user's question directly, without elaboration, explanation, or details unless asked.
+- Avoid introductions, conclusions, and explanations. One word answers are best when appropriate.
+- Your responses will be displayed on a command line interface. Use GitHub-flavored markdown for formatting.
+
+# Professional objectivity
+Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. Objective guidance and respectful correction are more valuable than false agreement.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume that a given library is available. Check that this codebase already uses the given library first.
+- When editing code, first look at surrounding context (especially imports) to understand frameworks and libraries in use.
+- Always follow security best practices. Never introduce code that exposes secrets or keys.
+
+# Code style
+- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.
+- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.
+
+# Doing tasks
+When performing software engineering tasks:
+1. Search to understand the codebase first.
+2. Implement using available tools.
+3. Verify the solution if possible.
+4. NEVER commit changes unless the user explicitly asks.
+
+# Tool usage policy
+- Prefer search tools over bash for file finding.
+- Batch independent tool calls together.
+- Reference code with \`file_path:line_number\` pattern.`;
+//# sourceMappingURL=anthropic.js.map

package/dist/system-context/prompts/anthropic.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"anthropic.js","sourceRoot":"","sources":["../../../src/system-context/prompts/anthropic.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDAiCyB,CAAC"}

package/dist/system-context/prompts/deepseek.d.ts

@@ -0,0 +1,2 @@
+export declare const DEEPSEEK_PROMPT = "You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\n\nIMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.\n\n# Tone and style\n- Be concise and direct. DeepSeek models are strong at reasoning \u2014 use this for complex analysis, but keep output focused.\n- Avoid long chains of reasoning in visible output. Use tool calls to verify assumptions rather than speculating.\n- Answer the user's question directly, without elaboration or explanation unless asked.\n- Your output is displayed on a command line interface. Use GitHub-flavored markdown.\n- Only use emojis if the user explicitly requests it.\n\n# Action-oriented reasoning\n- Think step by step internally, but take concrete actions (tool calls) to make progress.\n- When analyzing a problem, use search/read tools to gather facts before proposing solutions.\n- After getting tool results, immediately determine the next action rather than narrating what happened.\n- If you're unsure, use a tool to verify rather than asking the user.\n\n# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume a given library is available. Check the codebase first.\n- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.\n- Always follow security best practices. Never introduce code that exposes secrets or keys.\n\n# Code style\n- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.\n- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.\n\n# Doing tasks\n1. Search to understand the codebase first.\n2. Implement using available tools.\n3. Verify the solution if possible.\n4. NEVER commit changes unless the user explicitly asks.\n\n# Tool usage policy\n- Prefer search tools over bash for file finding.\n- Batch independent tool calls together.\n- Reference code with `file_path:line_number` pattern.";
+//# sourceMappingURL=deepseek.d.ts.map

package/dist/system-context/prompts/deepseek.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"deepseek.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/deepseek.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,eAAe,uzEAoC6B,CAAC"}

package/dist/system-context/prompts/deepseek.js

@@ -0,0 +1,38 @@
+export const DEEPSEEK_PROMPT = `You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+
+# Tone and style
+- Be concise and direct. DeepSeek models are strong at reasoning — use this for complex analysis, but keep output focused.
+- Avoid long chains of reasoning in visible output. Use tool calls to verify assumptions rather than speculating.
+- Answer the user's question directly, without elaboration or explanation unless asked.
+- Your output is displayed on a command line interface. Use GitHub-flavored markdown.
+- Only use emojis if the user explicitly requests it.
+
+# Action-oriented reasoning
+- Think step by step internally, but take concrete actions (tool calls) to make progress.
+- When analyzing a problem, use search/read tools to gather facts before proposing solutions.
+- After getting tool results, immediately determine the next action rather than narrating what happened.
+- If you're unsure, use a tool to verify rather than asking the user.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume a given library is available. Check the codebase first.
+- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.
+- Always follow security best practices. Never introduce code that exposes secrets or keys.
+
+# Code style
+- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.
+- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.
+
+# Doing tasks
+1. Search to understand the codebase first.
+2. Implement using available tools.
+3. Verify the solution if possible.
+4. NEVER commit changes unless the user explicitly asks.
+
+# Tool usage policy
+- Prefer search tools over bash for file finding.
+- Batch independent tool calls together.
+- Reference code with \`file_path:line_number\` pattern.`;
+//# sourceMappingURL=deepseek.js.map

package/dist/system-context/prompts/deepseek.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"deepseek.js","sourceRoot":"","sources":["../../../src/system-context/prompts/deepseek.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDAoC0B,CAAC"}

package/dist/system-context/prompts/default.d.ts

@@ -0,0 +1,2 @@
+export declare const DEFAULT_PROMPT = "You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\n\nIMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.\n\n# Tone and style\nYou should be concise, direct, and to the point. Remember that your output will be displayed on a command line interface. Your responses can use GitHub-flavored markdown for formatting.\nOutput text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools as means to communicate with the user during the session.\nIf you cannot or will not help the user with something, please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.\nOnly use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.\nIMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request.\nIMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.\nIMPORTANT: Keep your responses short. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations.\n\n# Proactiveness\nYou are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:\n1. Doing the right thing when asked, including taking actions and follow-up actions\n2. Not surprising the user with actions you take without asking\nFor example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.\n3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.\n\n# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library.\n- When you create a new component, first look at existing components to see how they're written.\n- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries.\n- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.\n\n# Code style\n- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks you to add them.\n- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required or there is no existing file that fits.\n\n# Doing tasks\nWhen performing software engineering tasks:\n1. Use the available search tools to understand the codebase and the user's query.\n2. Implement the solution using all tools available to you.\n3. Verify the solution if possible.\n4. NEVER commit changes unless the user explicitly asks you to.\n\n# Tool usage policy\n- When doing file search, prefer to use search tools rather than bash commands.\n- When making multiple tool calls that are independent, batch them together.\n- When referencing specific functions or pieces of code, include the pattern `file_path:line_number` to allow the user to easily navigate to the source code location.";
+//# sourceMappingURL=default.d.ts.map

package/dist/system-context/prompts/default.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"default.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/default.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,cAAc,umIAyC8I,CAAC"}

package/dist/system-context/prompts/default.js

@@ -0,0 +1,43 @@
+export const DEFAULT_PROMPT = `You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+
+# Tone and style
+You should be concise, direct, and to the point. Remember that your output will be displayed on a command line interface. Your responses can use GitHub-flavored markdown for formatting.
+Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools as means to communicate with the user during the session.
+If you cannot or will not help the user with something, please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
+Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request.
+IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
+IMPORTANT: Keep your responses short. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations.
+
+# Proactiveness
+You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
+1. Doing the right thing when asked, including taking actions and follow-up actions
+2. Not surprising the user with actions you take without asking
+For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
+3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library.
+- When you create a new component, first look at existing components to see how they're written.
+- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries.
+- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
+
+# Code style
+- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks you to add them.
+- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required or there is no existing file that fits.
+
+# Doing tasks
+When performing software engineering tasks:
+1. Use the available search tools to understand the codebase and the user's query.
+2. Implement the solution using all tools available to you.
+3. Verify the solution if possible.
+4. NEVER commit changes unless the user explicitly asks you to.
+
+# Tool usage policy
+- When doing file search, prefer to use search tools rather than bash commands.
+- When making multiple tool calls that are independent, batch them together.
+- When referencing specific functions or pieces of code, include the pattern \`file_path:line_number\` to allow the user to easily navigate to the source code location.`;
+//# sourceMappingURL=default.js.map

package/dist/system-context/prompts/default.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"default.js","sourceRoot":"","sources":["../../../src/system-context/prompts/default.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yKAyC2I,CAAC"}

package/dist/system-context/prompts/gemini.d.ts

@@ -0,0 +1,2 @@
+export declare const GEMINI_PROMPT = "You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\n\nIMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.\n\n# Tone and style\n- Be extremely concise and direct. Gemini responses tend to be verbose by default \u2014 actively counter this.\n- Avoid introductions, conclusions, explanations, and summaries unless the user explicitly asks.\n- Answer in as few words as possible. One-word answers are best when appropriate.\n- Your output is displayed on a command line interface. Use GitHub-flavored markdown.\n- Only use emojis if the user explicitly requests it.\n\n# Focus on action\n- Use tools immediately rather than explaining what you plan to do.\n- After running a tool, process the result and take the next step without commentary.\n- If the user asks a question, answer it directly rather than describing your approach.\n- NEVER add a \"summary\" or \"overview\" of what you did unless asked.\n\n# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume a given library is available. Check the codebase first.\n- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.\n- Always follow security best practices. Never introduce code that exposes secrets or keys.\n\n# Code style\n- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.\n- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.\n\n# Doing tasks\n1. Search to understand the codebase first.\n2. Implement using available tools.\n3. Verify the solution if possible.\n4. NEVER commit changes unless the user explicitly asks.\n\n# Tool usage policy\n- Prefer search tools over bash for file finding.\n- Batch independent tool calls together.\n- Reference code with `file_path:line_number` pattern.";
+//# sourceMappingURL=gemini.d.ts.map

package/dist/system-context/prompts/gemini.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"gemini.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/gemini.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,aAAa,ytEAoC+B,CAAC"}

package/dist/system-context/prompts/gemini.js

@@ -0,0 +1,38 @@
+export const GEMINI_PROMPT = `You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+
+# Tone and style
+- Be extremely concise and direct. Gemini responses tend to be verbose by default — actively counter this.
+- Avoid introductions, conclusions, explanations, and summaries unless the user explicitly asks.
+- Answer in as few words as possible. One-word answers are best when appropriate.
+- Your output is displayed on a command line interface. Use GitHub-flavored markdown.
+- Only use emojis if the user explicitly requests it.
+
+# Focus on action
+- Use tools immediately rather than explaining what you plan to do.
+- After running a tool, process the result and take the next step without commentary.
+- If the user asks a question, answer it directly rather than describing your approach.
+- NEVER add a "summary" or "overview" of what you did unless asked.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume a given library is available. Check the codebase first.
+- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.
+- Always follow security best practices. Never introduce code that exposes secrets or keys.
+
+# Code style
+- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.
+- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required or no existing file fits.
+
+# Doing tasks
+1. Search to understand the codebase first.
+2. Implement using available tools.
+3. Verify the solution if possible.
+4. NEVER commit changes unless the user explicitly asks.
+
+# Tool usage policy
+- Prefer search tools over bash for file finding.
+- Batch independent tool calls together.
+- Reference code with \`file_path:line_number\` pattern.`;
+//# sourceMappingURL=gemini.js.map

package/dist/system-context/prompts/gemini.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"gemini.js","sourceRoot":"","sources":["../../../src/system-context/prompts/gemini.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,aAAa,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDAoC4B,CAAC"}

package/dist/system-context/prompts/index.d.ts

@@ -0,0 +1,3 @@
+export type PromptVariant = "default" | "anthropic" | "openai" | "gemini" | "deepseek";
+export declare function selectPrompt(modelId?: string): string;
+//# sourceMappingURL=index.d.ts.map

package/dist/system-context/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/index.ts"],"names":[],"mappings":"AAMA,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,WAAW,GAAG,QAAQ,GAAG,QAAQ,GAAG,UAAU,CAAC;AAEvF,wBAAgB,YAAY,CAAC,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAkBrD"}

package/dist/system-context/prompts/index.js

@@ -0,0 +1,24 @@
+import { DEFAULT_PROMPT } from "./default.js";
+import { ANTHROPIC_PROMPT } from "./anthropic.js";
+import { OPENAI_PROMPT } from "./openai.js";
+import { GEMINI_PROMPT } from "./gemini.js";
+import { DEEPSEEK_PROMPT } from "./deepseek.js";
+export function selectPrompt(modelId) {
+    if (!modelId)
+        return DEFAULT_PROMPT;
+    const id = modelId.toLowerCase();
+    if (id.includes("claude") || id.includes("anthropic")) {
+        return ANTHROPIC_PROMPT;
+    }
+    if (id.includes("gpt") || id.includes("o1") || id.includes("o3") || id.includes("openai")) {
+        return OPENAI_PROMPT;
+    }
+    if (id.includes("gemini")) {
+        return GEMINI_PROMPT;
+    }
+    if (id.includes("deepseek")) {
+        return DEEPSEEK_PROMPT;
+    }
+    return DEFAULT_PROMPT;
+}
+//# sourceMappingURL=index.js.map

package/dist/system-context/prompts/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/system-context/prompts/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAE,MAAM,cAAc,CAAC;AAC9C,OAAO,EAAE,gBAAgB,EAAE,MAAM,gBAAgB,CAAC;AAClD,OAAO,EAAE,aAAa,EAAE,MAAM,aAAa,CAAC;AAC5C,OAAO,EAAE,aAAa,EAAE,MAAM,aAAa,CAAC;AAC5C,OAAO,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC;AAIhD,MAAM,UAAU,YAAY,CAAC,OAAgB;IAC3C,IAAI,CAAC,OAAO;QAAE,OAAO,cAAc,CAAC;IACpC,MAAM,EAAE,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC;IAEjC,IAAI,EAAE,CAAC,QAAQ,CAAC,QAAQ,CAAC,IAAI,EAAE,CAAC,QAAQ,CAAC,WAAW,CAAC,EAAE,CAAC;QACtD,OAAO,gBAAgB,CAAC;IAC1B,CAAC;IACD,IAAI,EAAE,CAAC,QAAQ,CAAC,KAAK,CAAC,IAAI,EAAE,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC1F,OAAO,aAAa,CAAC;IACvB,CAAC;IACD,IAAI,EAAE,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC1B,OAAO,aAAa,CAAC;IACvB,CAAC;IACD,IAAI,EAAE,CAAC,QAAQ,CAAC,UAAU,CAAC,EAAE,CAAC;QAC5B,OAAO,eAAe,CAAC;IACzB,CAAC;IAED,OAAO,cAAc,CAAC;AACxB,CAAC"}

package/dist/system-context/prompts/openai.d.ts

@@ -0,0 +1,2 @@
+export declare const OPENAI_PROMPT = "You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. You should keep going until the user's query is completely resolved, before ending your turn.\n\nYour thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.\n\nYou MUST iterate and keep going until the problem is solved. You have everything you need to resolve this problem. Fully solve it autonomously.\n\nOnly terminate your turn when you are sure that the problem is solved. Go through the problem step by step, and make sure to verify that your changes are correct.\n\nIMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming.\n\n# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume that a given library is available. Check that this codebase already uses it first.\n- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.\n- Always follow security best practices.\n\n# Code style\n- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.\n- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required.\n\n# Doing tasks\n1. Search to understand the codebase first.\n2. Implement using available tools.\n3. Verify the solution.\n4. NEVER commit changes unless the user explicitly asks.\n\n# Tool usage policy\n- Prefer search tools over bash for file finding.\n- Batch independent tool calls together.\n- Reference code with `file_path:line_number` pattern.";
+//# sourceMappingURL=openai.d.ts.map

package/dist/system-context/prompts/openai.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"openai.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/openai.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,aAAa,oyDA6B+B,CAAC"}

package/dist/system-context/prompts/openai.js

@@ -0,0 +1,31 @@
+export const OPENAI_PROMPT = `You are VNT Agent, an interactive CLI tool that helps users with software engineering tasks. You should keep going until the user's query is completely resolved, before ending your turn.
+
+Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.
+
+You MUST iterate and keep going until the problem is solved. You have everything you need to resolve this problem. Fully solve it autonomously.
+
+Only terminate your turn when you are sure that the problem is solved. Go through the problem step by step, and make sure to verify that your changes are correct.
+
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume that a given library is available. Check that this codebase already uses it first.
+- When editing code, look at surrounding context (especially imports) to understand frameworks and libraries in use.
+- Always follow security best practices.
+
+# Code style
+- DO NOT ADD comments to code unless the original code already has extensive comments or the user asks.
+- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required.
+
+# Doing tasks
+1. Search to understand the codebase first.
+2. Implement using available tools.
+3. Verify the solution.
+4. NEVER commit changes unless the user explicitly asks.
+
+# Tool usage policy
+- Prefer search tools over bash for file finding.
+- Batch independent tool calls together.
+- Reference code with \`file_path:line_number\` pattern.`;
+//# sourceMappingURL=openai.js.map

package/dist/system-context/prompts/openai.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"openai.js","sourceRoot":"","sources":["../../../src/system-context/prompts/openai.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,aAAa,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDA6B4B,CAAC"}

package/dist/system-context/prompts/system-prompt-source.d.ts

@@ -0,0 +1,3 @@
+import type { ContextSourceValue } from "../types.js";
+export declare function createSystemPromptSource(getModelId: () => string | undefined): ContextSourceValue<string>;
+//# sourceMappingURL=system-prompt-source.d.ts.map

package/dist/system-context/prompts/system-prompt-source.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-prompt-source.d.ts","sourceRoot":"","sources":["../../../src/system-context/prompts/system-prompt-source.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAoB,MAAM,aAAa,CAAC;AAGxE,wBAAgB,wBAAwB,CACtC,UAAU,EAAE,MAAM,MAAM,GAAG,SAAS,GACnC,kBAAkB,CAAC,MAAM,CAAC,CAkB5B"}

package/dist/system-context/prompts/system-prompt-source.js

@@ -0,0 +1,21 @@
+import { selectPrompt } from "./index.js";
+export function createSystemPromptSource(getModelId) {
+    return {
+        key: "core.system-prompt",
+        priority: 0,
+        async load() {
+            const modelId = getModelId();
+            return selectPrompt(modelId);
+        },
+        renderBaseline(value) {
+            return value;
+        },
+        renderUpdate() {
+            return null;
+        },
+        renderRemoval() {
+            return "";
+        },
+    };
+}
+//# sourceMappingURL=system-prompt-source.js.map

package/dist/system-context/prompts/system-prompt-source.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-prompt-source.js","sourceRoot":"","sources":["../../../src/system-context/prompts/system-prompt-source.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAE1C,MAAM,UAAU,wBAAwB,CACtC,UAAoC;IAEpC,OAAO;QACL,GAAG,EAAE,oBAAwC;QAC7C,QAAQ,EAAE,CAAC;QACX,KAAK,CAAC,IAAI;YACR,MAAM,OAAO,GAAG,UAAU,EAAE,CAAC;YAC7B,OAAO,YAAY,CAAC,OAAO,CAAC,CAAC;QAC/B,CAAC;QACD,cAAc,CAAC,KAAK;YAClB,OAAO,KAAK,CAAC;QACf,CAAC;QACD,YAAY;YACV,OAAO,IAAI,CAAC;QACd,CAAC;QACD,aAAa;YACX,OAAO,EAAE,CAAC;QACZ,CAAC;KACF,CAAC;AACJ,CAAC"}

package/dist/system-context/registry.d.ts

@@ -0,0 +1,3 @@
+import type { ContextRegistry } from "./types.js";
+export declare function createContextRegistry(): ContextRegistry;
+//# sourceMappingURL=registry.d.ts.map

package/dist/system-context/registry.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"registry.d.ts","sourceRoot":"","sources":["../../src/system-context/registry.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAyF,eAAe,EAAE,MAAM,YAAY,CAAC;AAEzI,wBAAgB,qBAAqB,IAAI,eAAe,CAuEvD"}

package/dist/system-context/registry.js

@@ -0,0 +1,73 @@
+export function createContextRegistry() {
+    const sources = new Map();
+    let initialized = false;
+    let snapshots = new Map();
+    return {
+        register(source) {
+            sources.set(source.key, source);
+        },
+        unregister(key) {
+            sources.delete(key);
+        },
+        async initialize() {
+            const entries = [];
+            const newSnapshots = new Map();
+            const sorted = [...sources.values()].sort((a, b) => (a.priority ?? 100) - (b.priority ?? 100));
+            for (const source of sorted) {
+                const value = await source.load();
+                const rendered = source.renderBaseline(value);
+                if (rendered) {
+                    entries.push(rendered);
+                }
+                newSnapshots.set(source.key, { key: source.key, value, rendered });
+            }
+            snapshots = newSnapshots;
+            initialized = true;
+            return {
+                baseline: entries.join("\n\n"),
+                snapshots: snapshots,
+            };
+        },
+        async reconcile() {
+            if (!initialized) {
+                const ctx = await this.initialize();
+                return { type: "replaced", systemContext: ctx };
+            }
+            const updates = [];
+            let changed = false;
+            const newSnapshots = new Map(snapshots);
+            for (const [, source] of sources) {
+                const current = await source.load();
+                const prev = snapshots.get(source.key);
+                if (prev && !shallowEqual(prev.value, current)) {
+                    const update = source.renderUpdate(current, prev.value);
+                    if (update) {
+                        updates.push(update);
+                        newSnapshots.set(source.key, { key: source.key, value: current, rendered: update });
+                        changed = true;
+                    }
+                }
+            }
+            if (!changed) {
+                return { type: "unchanged" };
+            }
+            return {
+                type: "updated",
+                update: updates.join("\n\n"),
+                snapshot: { key: "", value: null, rendered: updates.join("\n\n") },
+            };
+        },
+    };
+}
+function shallowEqual(a, b) {
+    if (a === b)
+        return true;
+    if (typeof a !== "object" || typeof b !== "object" || a === null || b === null)
+        return false;
+    const ka = Object.keys(a);
+    const kb = Object.keys(b);
+    if (ka.length !== kb.length)
+        return false;
+    return ka.every((k) => a[k] === b[k]);
+}
+//# sourceMappingURL=registry.js.map

package/dist/system-context/registry.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"registry.js","sourceRoot":"","sources":["../../src/system-context/registry.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,qBAAqB;IACnC,MAAM,OAAO,GAAG,IAAI,GAAG,EAAwC,CAAC;IAChE,IAAI,WAAW,GAAG,KAAK,CAAC;IACxB,IAAI,SAAS,GAAG,IAAI,GAAG,EAAqC,CAAC;IAE7D,OAAO;QACL,QAAQ,CAAC,MAA0B;YACjC,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC,GAAG,EAAE,MAAM,CAAC,CAAC;QAClC,CAAC;QAED,UAAU,CAAC,GAAqB;YAC9B,OAAO,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC;QACtB,CAAC;QAED,KAAK,CAAC,UAAU;YACd,MAAM,OAAO,GAAa,EAAE,CAAC;YAC7B,MAAM,YAAY,GAAG,IAAI,GAAG,EAAqC,CAAC;YAElE,MAAM,MAAM,GAAG,CAAC,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,QAAQ,IAAI,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,QAAQ,IAAI,GAAG,CAAC,CAAC,CAAC;YAC/F,KAAK,MAAM,MAAM,IAAI,MAAM,EAAE,CAAC;gBAC5B,MAAM,KAAK,GAAG,MAAM,MAAM,CAAC,IAAI,EAAE,CAAC;gBAClC,MAAM,QAAQ,GAAG,MAAM,CAAC,cAAc,CAAC,KAAK,CAAC,CAAC;gBAC9C,IAAI,QAAQ,EAAE,CAAC;oBACb,OAAO,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;gBACzB,CAAC;gBACD,YAAY,CAAC,GAAG,CAAC,MAAM,CAAC,GAAG,EAAE,EAAE,GAAG,EAAE,MAAM,CAAC,GAAG,EAAE,KAAK,EAAE,QAAQ,EAAE,CAAC,CAAC;YACrE,CAAC;YAED,SAAS,GAAG,YAAY,CAAC;YACzB,WAAW,GAAG,IAAI,CAAC;YAEnB,OAAO;gBACL,QAAQ,EAAE,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC;gBAC9B,SAAS,EAAE,SAAS;aACrB,CAAC;QACJ,CAAC;QAED,KAAK,CAAC,SAAS;YACb,IAAI,CAAC,WAAW,EAAE,CAAC;gBACjB,MAAM,GAAG,GAAG,MAAM,IAAI,CAAC,UAAU,EAAE,CAAC;gBACpC,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,aAAa,EAAE,GAAG,EAAE,CAAC;YAClD,CAAC;YAED,MAAM,OAAO,GAAa,EAAE,CAAC;YAC7B,IAAI,OAAO,GAAG,KAAK,CAAC;YACpB,MAAM,YAAY,GAAG,IAAI,GAAG,CAAC,SAAS,CAAC,CAAC;YAExC,KAAK,MAAM,CAAC,EAAE,MAAM,CAAC,IAAI,OAAO,EAAE,CAAC;gBACjC,MAAM,OAAO,GAAG,MAAM,MAAM,CAAC,IAAI,EAAE,CAAC;gBACpC,MAAM,IAAI,GAAG,SAAS,CAAC,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC;gBACvC,IAAI,IAAI,IAAI,CAAC,YAAY,CAAC,IAAI,CAAC,KAAK,EAAE,OAAO,CAAC,EAAE,CAAC;oBAC/C,MAAM,MAAM,GAAG,MAAM,CAAC,YAAY,CAAC,OAAO,EAAE,IAAI,CAAC,KAAK,CAAC,CAAC;oBACxD,IAAI,MAAM,EAAE,CAAC;wBACX,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;wBACrB,YAAY,CAAC,GAAG,CAAC,MAAM,CAAC,GAAG,EAAE,EAAE,GAAG,EAAE,MAAM,CAAC,GAAG,EAAE,KAAK,EAAE,OAAO,EAAE,QAAQ,EAAE,MAAM,EAAE,CAAC,CAAC;wBACpF,OAAO,GAAG,IAAI,CAAC;oBACjB,CAAC;gBACH,CAAC;YACH,CAAC;YAED,IAAI,CAAC,OAAO,EAAE,CAAC;gBACb,OAAO,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC;YAC/B,CAAC;YAED,OAAO;gBACL,IAAI,EAAE,SAAS;gBACf,MAAM,EAAE,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC;gBAC5B,QAAQ,EAAE,EAAE,GAAG,EAAE,EAAsB,EAAE,KAAK,EAAE,IAAI,EAAE,QAAQ,EAAE,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE;aACvF,CAAC;QACJ,CAAC;KACF,CAAC;AACJ,CAAC;AAED,SAAS,YAAY,CAAC,CAAU,EAAE,CAAU;IAC1C,IAAI,CAAC,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IACzB,IAAI,OAAO,CAAC,KAAK,QAAQ,IAAI,OAAO,CAAC,KAAK,QAAQ,IAAI,CAAC,KAAK,IAAI,IAAI,CAAC,KAAK,IAAI;QAAE,OAAO,KAAK,CAAC;IAC7F,MAAM,EAAE,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC1B,MAAM,EAAE,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC1B,IAAI,EAAE,CAAC,MAAM,KAAK,EAAE,CAAC,MAAM;QAAE,OAAO,KAAK,CAAC;IAC1C,OAAO,EAAE,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,EAAE,CAAE,CAA6B,CAAC,CAAC,CAAC,KAAM,CAA6B,CAAC,CAAC,CAAC,CAAC,CAAC;AAClG,CAAC"}

package/dist/system-context/sources/agent-source.d.ts

@@ -0,0 +1,14 @@
+import type { ContextSourceValue } from "../types.js";
+import type { AgentRegistry } from "../../agent/agent-registry.js";
+export interface AgentContextInfo {
+    currentAgentId: string | null;
+    agents: Array<{
+        id: string;
+        name: string;
+        description: string;
+        mode: string;
+        capabilities: string[];
+    }>;
+}
+export declare function createAgentSource(registry: AgentRegistry, getCurrentAgentId: () => string | null): ContextSourceValue<AgentContextInfo>;
+//# sourceMappingURL=agent-source.d.ts.map

package/dist/system-context/sources/agent-source.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-source.d.ts","sourceRoot":"","sources":["../../../src/system-context/sources/agent-source.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAoB,MAAM,aAAa,CAAC;AACxE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAEnE,MAAM,WAAW,gBAAgB;IAC/B,cAAc,EAAE,MAAM,GAAG,IAAI,CAAC;IAC9B,MAAM,EAAE,KAAK,CAAC;QACZ,EAAE,EAAE,MAAM,CAAC;QACX,IAAI,EAAE,MAAM,CAAC;QACb,WAAW,EAAE,MAAM,CAAC;QACpB,IAAI,EAAE,MAAM,CAAC;QACb,YAAY,EAAE,MAAM,EAAE,CAAC;KACxB,CAAC,CAAC;CACJ;AAED,wBAAgB,iBAAiB,CAAC,QAAQ,EAAE,aAAa,EAAE,iBAAiB,EAAE,MAAM,MAAM,GAAG,IAAI,GAAG,kBAAkB,CAAC,gBAAgB,CAAC,CAgDvI"}

package/dist/system-context/sources/agent-source.js

@@ -0,0 +1,50 @@
+export function createAgentSource(registry, getCurrentAgentId) {
+    return {
+        key: "core.agents",
+        priority: 20,
+        async load() {
+            const agents = await registry.list();
+            return {
+                currentAgentId: getCurrentAgentId(),
+                agents: agents.map((a) => ({
+                    id: a.id,
+                    name: a.profile.name,
+                    description: a.profile.description,
+                    mode: a.permissions?.mode ?? "primary",
+                    capabilities: [...(a.capabilities.tools ?? []), ...(a.capabilities.models ?? [])],
+                })),
+            };
+        },
+        renderBaseline(value) {
+            const lines = ["## Agents"];
+            if (value.currentAgentId) {
+                const current = value.agents.find((a) => a.id === value.currentAgentId);
+                if (current) {
+                    lines.push(`- **Current agent**: ${current.name} (${current.mode}) — ${current.description}`);
+                }
+            }
+            const others = value.agents.filter((a) => a.id !== value.currentAgentId);
+            if (others.length > 0) {
+                lines.push("**Available agents:**");
+                for (const a of others) {
+                    const caps = a.capabilities.length > 0 ? ` [${a.capabilities.join(", ")}]` : "";
+                    lines.push(`- \`${a.id}\`: ${a.name} (${a.mode})${caps} — ${a.description}`);
+                }
+            }
+            return lines.join("\n");
+        },
+        renderUpdate(value, previous) {
+            if (value.currentAgentId !== previous.currentAgentId) {
+                const current = value.agents.find((a) => a.id === value.currentAgentId);
+                if (current) {
+                    return `[Agent switched]\nNow using agent: ${current.name} (${current.mode}).`;
+                }
+            }
+            return null;
+        },
+        renderRemoval() {
+            return "";
+        },
+    };
+}
+//# sourceMappingURL=agent-source.js.map

package/dist/system-context/sources/agent-source.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-source.js","sourceRoot":"","sources":["../../../src/system-context/sources/agent-source.ts"],"names":[],"mappings":"AAcA,MAAM,UAAU,iBAAiB,CAAC,QAAuB,EAAE,iBAAsC;IAC/F,OAAO;QACL,GAAG,EAAE,aAAiC;QACtC,QAAQ,EAAE,EAAE;QACZ,KAAK,CAAC,IAAI;YACR,MAAM,MAAM,GAAG,MAAM,QAAQ,CAAC,IAAI,EAAE,CAAC;YACrC,OAAO;gBACL,cAAc,EAAE,iBAAiB,EAAE;gBACnC,MAAM,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;oBACzB,EAAE,EAAE,CAAC,CAAC,EAAE;oBACR,IAAI,EAAE,CAAC,CAAC,OAAO,CAAC,IAAI;oBACpB,WAAW,EAAE,CAAC,CAAC,OAAO,CAAC,WAAW;oBAClC,IAAI,EAAE,CAAC,CAAC,WAAW,EAAE,IAAI,IAAI,SAAS;oBACtC,YAAY,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,YAAY,CAAC,KAAK,IAAI,EAAE,CAAC,EAAE,GAAG,CAAC,CAAC,CAAC,YAAY,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC;iBAClF,CAAC,CAAC;aACJ,CAAC;QACJ,CAAC;QACD,cAAc,CAAC,KAAK;YAClB,MAAM,KAAK,GAAa,CAAC,WAAW,CAAC,CAAC;YACtC,IAAI,KAAK,CAAC,cAAc,EAAE,CAAC;gBACzB,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,KAAK,CAAC,cAAc,CAAC,CAAC;gBACxE,IAAI,OAAO,EAAE,CAAC;oBACZ,KAAK,CAAC,IAAI,CAAC,wBAAwB,OAAO,CAAC,IAAI,KAAK,OAAO,CAAC,IAAI,OAAO,OAAO,CAAC,WAAW,EAAE,CAAC,CAAC;gBAChG,CAAC;YACH,CAAC;YACD,MAAM,MAAM,GAAG,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,KAAK,CAAC,cAAc,CAAC,CAAC;YACzE,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;gBACtB,KAAK,CAAC,IAAI,CAAC,uBAAuB,CAAC,CAAC;gBACpC,KAAK,MAAM,CAAC,IAAI,MAAM,EAAE,CAAC;oBACvB,MAAM,IAAI,GAAG,CAAC,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,YAAY,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;oBAChF,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,EAAE,OAAO,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,IAAI,IAAI,IAAI,MAAM,CAAC,CAAC,WAAW,EAAE,CAAC,CAAC;gBAC/E,CAAC;YACH,CAAC;YACD,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAC1B,CAAC;QACD,YAAY,CAAC,KAAK,EAAE,QAAQ;YAC1B,IAAI,KAAK,CAAC,cAAc,KAAK,QAAQ,CAAC,cAAc,EAAE,CAAC;gBACrD,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,KAAK,CAAC,cAAc,CAAC,CAAC;gBACxE,IAAI,OAAO,EAAE,CAAC;oBACZ,OAAO,sCAAsC,OAAO,CAAC,IAAI,KAAK,OAAO,CAAC,IAAI,IAAI,CAAC;gBACjF,CAAC;YACH,CAAC;YACD,OAAO,IAAI,CAAC;QACd,CAAC;QACD,aAAa;YACX,OAAO,EAAE,CAAC;QACZ,CAAC;KACF,CAAC;AACJ,CAAC"}

package/dist/system-context/sources/date-source.d.ts

@@ -0,0 +1,7 @@
+import type { ContextSourceValue } from "../types.js";
+export declare function createDateSource(): ContextSourceValue<{
+    date: string;
+    time: string;
+    timezone: string;
+}>;
+//# sourceMappingURL=date-source.d.ts.map

package/dist/system-context/sources/date-source.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"date-source.d.ts","sourceRoot":"","sources":["../../../src/system-context/sources/date-source.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAoB,MAAM,aAAa,CAAC;AAExE,wBAAgB,gBAAgB,IAAI,kBAAkB,CAAC;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAC,CAuBvG"}

package/dist/system-context/sources/date-source.js

@@ -0,0 +1,26 @@
+export function createDateSource() {
+    return {
+        key: "core.date",
+        priority: 30,
+        async load() {
+            const now = new Date();
+            return {
+                date: now.toLocaleDateString("en-US", { weekday: "long", year: "numeric", month: "long", day: "numeric" }),
+                time: now.toLocaleTimeString("en-US"),
+                timezone: Intl.DateTimeFormat().resolvedOptions().timeZone,
+            };
+        },
+        renderBaseline(value) {
+            return `## Current Date & Time\n- Date: ${value.date}\n- Time: ${value.time}\n- Timezone: ${value.timezone}`;
+        },
+        renderUpdate(value, previous) {
+            if (value.date === previous.date)
+                return null;
+            return `[Context update — date changed]\nThe current date is now ${value.date}.`;
+        },
+        renderRemoval() {
+            return "[Context source removed: date]";
+        },
+    };
+}
+//# sourceMappingURL=date-source.js.map

package/dist/system-context/sources/date-source.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"date-source.js","sourceRoot":"","sources":["../../../src/system-context/sources/date-source.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,gBAAgB;IAC9B,OAAO;QACL,GAAG,EAAE,WAA+B;QACpC,QAAQ,EAAE,EAAE;QACZ,KAAK,CAAC,IAAI;YACR,MAAM,GAAG,GAAG,IAAI,IAAI,EAAE,CAAC;YACvB,OAAO;gBACL,IAAI,EAAE,GAAG,CAAC,kBAAkB,CAAC,OAAO,EAAE,EAAE,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,EAAE,SAAS,EAAE,CAAC;gBAC1G,IAAI,EAAE,GAAG,CAAC,kBAAkB,CAAC,OAAO,CAAC;gBACrC,QAAQ,EAAE,IAAI,CAAC,cAAc,EAAE,CAAC,eAAe,EAAE,CAAC,QAAQ;aAC3D,CAAC;QACJ,CAAC;QACD,cAAc,CAAC,KAAK;YAClB,OAAO,mCAAmC,KAAK,CAAC,IAAI,aAAa,KAAK,CAAC,IAAI,iBAAiB,KAAK,CAAC,QAAQ,EAAE,CAAC;QAC/G,CAAC;QACD,YAAY,CAAC,KAAK,EAAE,QAAQ;YAC1B,IAAI,KAAK,CAAC,IAAI,KAAK,QAAQ,CAAC,IAAI;gBAAE,OAAO,IAAI,CAAC;YAC9C,OAAO,4DAA4D,KAAK,CAAC,IAAI,GAAG,CAAC;QACnF,CAAC;QACD,aAAa;YACX,OAAO,gCAAgC,CAAC;QAC1C,CAAC;KACF,CAAC;AACJ,CAAC"}

package/dist/system-context/sources/instructions-source.d.ts

@@ -0,0 +1,8 @@
+import type { ContextSourceValue } from "../types.js";
+export interface InstructionsInfo {
+    global: string;
+    project: string;
+    effective: string;
+}
+export declare function createInstructionsSource(cwd?: string | (() => string)): ContextSourceValue<InstructionsInfo>;
+//# sourceMappingURL=instructions-source.d.ts.map

package/dist/system-context/sources/instructions-source.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"instructions-source.d.ts","sourceRoot":"","sources":["../../../src/system-context/sources/instructions-source.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,kBAAkB,EAAoB,MAAM,aAAa,CAAC;AAKxE,MAAM,WAAW,gBAAgB;IAC/B,MAAM,EAAE,MAAM,CAAC;IACf,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,wBAAwB,CAAC,GAAG,CAAC,EAAE,MAAM,GAAG,CAAC,MAAM,MAAM,CAAC,GAAG,kBAAkB,CAAC,gBAAgB,CAAC,CAiC5G"}