@mastra/code-sdk 0.0.0-client-tool-results-20260912062135

package/dist/agents/modes/explore.js

@@ -0,0 +1,42 @@
+import { EXPLORE_MODE_AVAILABLE_TOOLS } from "../tool-availability.js";
+//#region src/agents/modes/explore.ts
+const fastMode = {
+	id: "fast",
+	name: "Explore",
+	description: "Read-only codebase exploration. Use for questions like 'find all usages of X', 'how does module Y work'.",
+	defaultModelId: "openai/gpt-5.4-mini",
+	instructions: `You are an expert code explorer. Your job is to investigate a codebase and answer a specific question or gather specific information.
+
+## Rules
+- You have READ-ONLY access. You cannot modify files or run commands.
+- Be thorough — search broadly first, then drill into relevant files.
+- After gathering enough information, produce a clear, concise summary of your findings.
+
+## Tool Strategy
+- **Start broad**: Use find_files (glob) to understand project structure
+- **Search smart**: Use search_content (grep) with specific patterns — avoid overly broad searches
+- **Read efficiently**: Use view with view_range for large files — don't read entire files if you only need a section
+- **Parallelize**: Make multiple independent tool calls in one round when exploring different areas
+
+## Efficiency
+Your output returns to the parent agent. Be concise:
+- Don't include raw file contents in your response — summarize what you found
+- Reference files by path and line number, not by copying code
+- If a search returns many results, report the count and key examples, not every match
+
+## Output Format
+End with a structured summary:
+. **Answer**: Direct answer to the question (1-2 sentences)
+. **Key Files**: Most relevant files with line numbers
+. **Details**: Additional context if needed
+
+Keep your summary under 300 words.
+
+## Workflows
+- You can use \`list-workflows\` and \`get-workflow\` to inspect saved workflows. You cannot create, run, or delete in this mode.`,
+	availableTools: [...EXPLORE_MODE_AVAILABLE_TOOLS]
+};
+//#endregion
+export { fastMode };
+
+//# sourceMappingURL=explore.js.map

package/dist/agents/modes/explore.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"explore.js","names":[],"sources":["../../../src/agents/modes/explore.ts"],"sourcesContent":["/**\n * Explore subagent — read-only codebase exploration.\n *\n * This subagent is given a focused task (e.g., \"find all usages of X\",\n * \"understand how module Y works\") and uses read-only tools to explore\n * the codebase, then returns a concise summary of its findings.\n */\nimport type { AgentControllerMode } from '@mastra/core/agent-controller';\nimport { EXPLORE_MODE_AVAILABLE_TOOLS } from '../tool-availability.js';\n\nexport const fastMode: AgentControllerMode = {\n  id: 'fast',\n  name: 'Explore',\n  description:\n    \"Read-only codebase exploration. Use for questions like 'find all usages of X', 'how does module Y work'.\",\n  defaultModelId: 'openai/gpt-5.4-mini',\n  instructions: `You are an expert code explorer. Your job is to investigate a codebase and answer a specific question or gather specific information.\n\n## Rules\n- You have READ-ONLY access. You cannot modify files or run commands.\n- Be thorough — search broadly first, then drill into relevant files.\n- After gathering enough information, produce a clear, concise summary of your findings.\n\n## Tool Strategy\n- **Start broad**: Use find_files (glob) to understand project structure\n- **Search smart**: Use search_content (grep) with specific patterns — avoid overly broad searches\n- **Read efficiently**: Use view with view_range for large files — don't read entire files if you only need a section\n- **Parallelize**: Make multiple independent tool calls in one round when exploring different areas\n\n## Efficiency\nYour output returns to the parent agent. Be concise:\n- Don't include raw file contents in your response — summarize what you found\n- Reference files by path and line number, not by copying code\n- If a search returns many results, report the count and key examples, not every match\n\n## Output Format\nEnd with a structured summary:\n. **Answer**: Direct answer to the question (1-2 sentences)\n. **Key Files**: Most relevant files with line numbers\n. **Details**: Additional context if needed\n\nKeep your summary under 300 words.\n\n## Workflows\n- You can use \\`list-workflows\\` and \\`get-workflow\\` to inspect saved workflows. You cannot create, run, or delete in this mode.`,\n\n  availableTools: [...EXPLORE_MODE_AVAILABLE_TOOLS],\n};\n"],"mappings":";;AAUA,MAAa,WAAgC;CAC3C,IAAI;CACJ,MAAM;CACN,aACE;CACF,gBAAgB;CAChB,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8Bd,gBAAgB,CAAC,GAAG,4BAA4B;AAClD"}

package/dist/agents/modes/plan.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Plan mode — read-only analysis and planning.
+ */
+import type { AgentControllerMode } from '@mastra/core/agent-controller';
+export declare const planMode: AgentControllerMode;
+//# sourceMappingURL=plan.d.ts.map

package/dist/agents/modes/plan.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"plan.d.ts","sourceRoot":"","sources":["../../../src/agents/modes/plan.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,+BAA+B,CAAC;AAGzE,eAAO,MAAM,QAAQ,EAAE,mBAwCtB,CAAC"}

package/dist/agents/modes/plan.js

@@ -0,0 +1,42 @@
+import { PLAN_MODE_AVAILABLE_TOOLS } from "../tool-availability.js";
+//#region src/agents/modes/plan.ts
+const planMode = {
+	id: "plan",
+	name: "Plan",
+	transitionsTo: "build",
+	defaultModelId: "openai/gpt-5.5",
+	description: "Read-only analysis and planning. Use for 'create an implementation plan for X', 'analyze the architecture of Y'.",
+	instructions: `You are an expert software architect and planner. Your job is to analyze a codebase and produce a detailed implementation plan for a given task.
+
+## Rules
+- You have READ-ONLY access to the project. You cannot modify project files or run commands.
+- The one exception is plan files: you can create and edit markdown files inside the session-specific plan directory identified in your system prompt using \`write_file\`, \`view\`, and \`string_replace_lsp\`. You may not write anywhere else.
+- First, explore the codebase to understand existing patterns, architecture, and conventions.
+- Produce a concrete, actionable plan — not vague suggestions.
+
+## Tool Strategy
+- **Discover structure**: Use find_files (glob) to understand project layout and find relevant files
+- **Find patterns**: Use search_content (grep) to locate existing implementations, imports, and conventions
+- **Understand deeply**: Use view with view_range to read specific sections of key files
+- **Parallelize**: Make multiple independent tool calls when exploring different areas
+
+## Plan Delivery
+- Write your plan to a markdown file in the session-specific plan directory identified in your system prompt using \`write_file\`, then call \`submit_plan({ path })\` with the path to that file (never the plan body).
+- Start the file with a \`# Title\` heading describing the plan.
+- Reuse the same file while iterating on the same plan; only create a new file for a genuinely different plan so each plan stays available to review.
+- Do NOT output the plan as text — it MUST live in the plan file.
+- Be concise: reference files by path and line number, don't include raw contents.
+- Focus on actionable details, not general observations.
+- To revise after "Request changes", edit the same file in place with \`string_replace_lsp\`, and call \`submit_plan\` again with the same path.
+
+## Workflows
+- You can INSPECT saved workflows via \`list-workflows\` and \`get-workflow\`.
+- You CANNOT build, run, or delete workflows in this mode.
+- If the user asks for a workflow design, include it in the implementation plan stored at the session-specific plan path, then call \`submit_plan({ path })\` as required above. After approval, build mode can save and run it.`,
+	metadata: { default: false },
+	availableTools: [...PLAN_MODE_AVAILABLE_TOOLS]
+};
+//#endregion
+export { planMode };
+
+//# sourceMappingURL=plan.js.map

package/dist/agents/modes/plan.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"plan.js","names":[],"sources":["../../../src/agents/modes/plan.ts"],"sourcesContent":["/**\n * Plan mode — read-only analysis and planning.\n */\nimport type { AgentControllerMode } from '@mastra/core/agent-controller';\nimport { PLAN_MODE_AVAILABLE_TOOLS } from '../tool-availability.js';\n\nexport const planMode: AgentControllerMode = {\n  id: 'plan',\n  name: 'Plan',\n  transitionsTo: 'build',\n  defaultModelId: 'openai/gpt-5.5',\n  description:\n    \"Read-only analysis and planning. Use for 'create an implementation plan for X', 'analyze the architecture of Y'.\",\n  instructions: `You are an expert software architect and planner. Your job is to analyze a codebase and produce a detailed implementation plan for a given task.\n\n## Rules\n- You have READ-ONLY access to the project. You cannot modify project files or run commands.\n- The one exception is plan files: you can create and edit markdown files inside the session-specific plan directory identified in your system prompt using \\`write_file\\`, \\`view\\`, and \\`string_replace_lsp\\`. You may not write anywhere else.\n- First, explore the codebase to understand existing patterns, architecture, and conventions.\n- Produce a concrete, actionable plan — not vague suggestions.\n\n## Tool Strategy\n- **Discover structure**: Use find_files (glob) to understand project layout and find relevant files\n- **Find patterns**: Use search_content (grep) to locate existing implementations, imports, and conventions\n- **Understand deeply**: Use view with view_range to read specific sections of key files\n- **Parallelize**: Make multiple independent tool calls when exploring different areas\n\n## Plan Delivery\n- Write your plan to a markdown file in the session-specific plan directory identified in your system prompt using \\`write_file\\`, then call \\`submit_plan({ path })\\` with the path to that file (never the plan body).\n- Start the file with a \\`# Title\\` heading describing the plan.\n- Reuse the same file while iterating on the same plan; only create a new file for a genuinely different plan so each plan stays available to review.\n- Do NOT output the plan as text — it MUST live in the plan file.\n- Be concise: reference files by path and line number, don't include raw contents.\n- Focus on actionable details, not general observations.\n- To revise after \"Request changes\", edit the same file in place with \\`string_replace_lsp\\`, and call \\`submit_plan\\` again with the same path.\n\n## Workflows\n- You can INSPECT saved workflows via \\`list-workflows\\` and \\`get-workflow\\`.\n- You CANNOT build, run, or delete workflows in this mode.\n- If the user asks for a workflow design, include it in the implementation plan stored at the session-specific plan path, then call \\`submit_plan({ path })\\` as required above. After approval, build mode can save and run it.`,\n\n  metadata: {\n    default: false,\n  },\n\n  availableTools: [...PLAN_MODE_AVAILABLE_TOOLS],\n};\n"],"mappings":";;AAMA,MAAa,WAAgC;CAC3C,IAAI;CACJ,MAAM;CACN,eAAe;CACf,gBAAgB;CAChB,aACE;CACF,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4Bd,UAAU,EACR,SAAS,MACX;CAEA,gBAAgB,CAAC,GAAG,yBAAyB;AAC/C"}

package/dist/agents/prompts/agent-instructions.d.ts

@@ -0,0 +1,70 @@
+/**
+ * Load project and global agent instruction files (AGENTS.md, CLAUDE.md).
+ * Prefers AGENTS.md over CLAUDE.md when multiple exist at the same location.
+ */
+export interface InstructionSource {
+    path: string;
+    content: string;
+    scope: 'global' | 'project';
+    /** Git ref the content was read from, when not read off the working tree. */
+    ref?: string;
+}
+/**
+ * Reads project-scope instruction files. The default implementation reads the
+ * working tree via `fs`; alternative readers can serve content from another
+ * source (e.g. a trusted git ref) while keeping working-tree paths as the
+ * addressing scheme.
+ */
+export interface InstructionFileReader {
+    exists(path: string): boolean;
+    read(path: string): string;
+    /** Git ref backing this reader, recorded on the loaded sources. */
+    ref?: string;
+}
+/**
+ * Create a reader that serves instruction files from a git ref instead of the
+ * working tree. Paths are still addressed as working-tree paths under
+ * `projectPath`; content comes from `git show <ref>:<relpath>` so an untrusted
+ * checkout (e.g. a PR branch under review) cannot influence what is loaded.
+ * Tries `origin/<ref>` first (remote truth), then the local ref. Any git
+ * failure (missing ref, missing file, no repo) reports the file as absent.
+ */
+export declare function createGitRefInstructionReader(projectPath: string, ref: string): InstructionFileReader;
+/**
+ * Reader for the reactive reminder channel (AgentsMDInjector) that serves
+ * paths under `projectPath` from a trusted git ref. Paths outside the project
+ * fall back to the operator machine's filesystem (those are trusted); paths
+ * inside the project are only ever resolved against the ref, never the
+ * working tree, so an untrusted checkout cannot feed content in.
+ */
+export declare function createGitRefReminderReader(projectPath: string, ref: string): {
+    pathExists: (path: string) => boolean;
+    isDirectory: (path: string) => boolean;
+    readFile: (path: string) => string;
+};
+/**
+ * Load all agent instruction files from global and project locations.
+ * Returns an array of instruction sources, with global ones first.
+ *
+ * `projectReader` controls where project-scope content comes from (defaults to
+ * the working tree). Global instructions read the operator machine's
+ * filesystem, unless `skipGlobal` keeps them out entirely.
+ */
+export declare function loadAgentInstructions(projectPath: string, configDirName?: string, projectReader?: InstructionFileReader, { skipGlobal }?: {
+    skipGlobal?: boolean;
+}): InstructionSource[];
+export declare function getStaticallyLoadedInstructionPaths(projectPath: string, configDirName?: string, projectReader?: InstructionFileReader): string[];
+/** Heading the agent-instructions block is introduced by in the system prompt. */
+export declare const AGENT_INSTRUCTIONS_HEADING = "# Agent Instructions";
+/**
+ * Format a single instruction source as it appears in the system prompt.
+ *
+ * Exported so callers that attribute prompt cost per source (the `/context`
+ * audit) measure the exact block that is sent rather than reconstructing it.
+ */
+export declare function formatInstructionSource(source: InstructionSource): string;
+/**
+ * Format loaded instructions into a string for the system prompt.
+ */
+export declare function formatAgentInstructions(sources: InstructionSource[]): string;
+//# sourceMappingURL=agent-instructions.d.ts.map

package/dist/agents/prompts/agent-instructions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-instructions.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/agent-instructions.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAoBH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,EAAE,QAAQ,GAAG,SAAS,CAAC;IAC5B,6EAA6E;IAC7E,GAAG,CAAC,EAAE,MAAM,CAAC;CACd;AAED;;;;;GAKG;AACH,MAAM,WAAW,qBAAqB;IACpC,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC;IAC9B,IAAI,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAAC;IAC3B,mEAAmE;IACnE,GAAG,CAAC,EAAE,MAAM,CAAC;CACd;AAOD;;;;;;;GAOG;AACH,wBAAgB,6BAA6B,CAAC,WAAW,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,qBAAqB,CA+BrG;AAED;;;;;;GAMG;AACH,wBAAgB,0BAA0B,CACxC,WAAW,EAAE,MAAM,EACnB,GAAG,EAAE,MAAM,GACV;IACD,UAAU,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;IACtC,WAAW,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;IACvC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC;CACpC,CA4CA;AAgBD;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CACnC,WAAW,EAAE,MAAM,EACnB,aAAa,SAAqB,EAClC,aAAa,GAAE,qBAA2C,EAC1D,EAAE,UAAkB,EAAE,GAAE;IAAE,UAAU,CAAC,EAAE,OAAO,CAAA;CAAO,GACpD,iBAAiB,EAAE,CAwDrB;AAED,wBAAgB,mCAAmC,CACjD,WAAW,EAAE,MAAM,EACnB,aAAa,SAAqB,EAClC,aAAa,CAAC,EAAE,qBAAqB,GACpC,MAAM,EAAE,CAEV;AAED,kFAAkF;AAClF,eAAO,MAAM,0BAA0B,yBAAyB,CAAC;AAEjE;;;;;GAKG;AACH,wBAAgB,uBAAuB,CAAC,MAAM,EAAE,iBAAiB,GAAG,MAAM,CAIzE;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,iBAAiB,EAAE,GAAG,MAAM,CAM5E"}

package/dist/agents/prompts/agent-instructions.js

@@ -0,0 +1,211 @@
+import { DEFAULT_CONFIG_DIR } from "../../constants.js";
+import { existsSync, readFileSync, statSync } from "fs";
+import { homedir } from "os";
+import { isAbsolute, join, normalize, relative, sep } from "path";
+import { execFileSync } from "child_process";
+//#region src/agents/prompts/agent-instructions.ts
+/**
+* Load project and global agent instruction files (AGENTS.md, CLAUDE.md).
+* Prefers AGENTS.md over CLAUDE.md when multiple exist at the same location.
+*/
+const INSTRUCTION_FILES = ["AGENTS.md", "CLAUDE.md"];
+const PROJECT_LOCATIONS = [
+	"",
+	".claude",
+	".mastracode"
+];
+const GLOBAL_LOCATIONS = [
+	".claude",
+	".mastracode",
+	".config/claude",
+	".config/mastracode"
+];
+const fsInstructionReader = {
+	exists: (path) => existsSync(path),
+	read: (path) => readFileSync(path, "utf-8")
+};
+/**
+* Create a reader that serves instruction files from a git ref instead of the
+* working tree. Paths are still addressed as working-tree paths under
+* `projectPath`; content comes from `git show <ref>:<relpath>` so an untrusted
+* checkout (e.g. a PR branch under review) cannot influence what is loaded.
+* Tries `origin/<ref>` first (remote truth), then the local ref. Any git
+* failure (missing ref, missing file, no repo) reports the file as absent.
+*/
+function createGitRefInstructionReader(projectPath, ref) {
+	const toRelative = (path) => {
+		const rel = relative(projectPath, path);
+		if (!rel || rel.startsWith("..") || isAbsolute(rel)) return null;
+		return rel.split(sep).join("/");
+	};
+	const show = (path) => {
+		const rel = toRelative(path);
+		if (rel === null) return null;
+		for (const candidate of [`origin/${ref}`, ref]) try {
+			return execFileSync("git", [
+				"-C",
+				projectPath,
+				"show",
+				`${candidate}:${rel}`
+			], {
+				encoding: "utf-8",
+				stdio: [
+					"ignore",
+					"pipe",
+					"ignore"
+				],
+				maxBuffer: 1024 * 1024
+			});
+		} catch {}
+		return null;
+	};
+	return {
+		ref,
+		exists: (path) => show(path) !== null,
+		read: (path) => {
+			const content = show(path);
+			if (content === null) throw new Error(`Not found at ref ${ref}: ${path}`);
+			return content;
+		}
+	};
+}
+/**
+* Reader for the reactive reminder channel (AgentsMDInjector) that serves
+* paths under `projectPath` from a trusted git ref. Paths outside the project
+* fall back to the operator machine's filesystem (those are trusted); paths
+* inside the project are only ever resolved against the ref, never the
+* working tree, so an untrusted checkout cannot feed content in.
+*/
+function createGitRefReminderReader(projectPath, ref) {
+	const gitReader = createGitRefInstructionReader(projectPath, ref);
+	const toRelative = (path) => {
+		const rel = relative(projectPath, normalize(path));
+		if (rel.startsWith("..") || isAbsolute(rel)) return null;
+		return rel.split(sep).join("/");
+	};
+	const objectType = (rel) => {
+		if (rel === "") return "tree";
+		for (const candidate of [`origin/${ref}`, ref]) try {
+			return execFileSync("git", [
+				"-C",
+				projectPath,
+				"cat-file",
+				"-t",
+				`${candidate}:${rel}`
+			], {
+				encoding: "utf-8",
+				stdio: [
+					"ignore",
+					"pipe",
+					"ignore"
+				]
+			}).trim();
+		} catch {}
+		return null;
+	};
+	return {
+		pathExists: (path) => {
+			const rel = toRelative(path);
+			if (rel === null) return existsSync(path);
+			return objectType(rel) !== null;
+		},
+		isDirectory: (path) => {
+			const rel = toRelative(path);
+			if (rel === null) try {
+				return statSync(path).isDirectory();
+			} catch {
+				return false;
+			}
+			return objectType(rel) === "tree";
+		},
+		readFile: (path) => {
+			if (toRelative(path) === null) return readFileSync(path, "utf-8");
+			return gitReader.read(path);
+		}
+	};
+}
+/**
+* Find the first existing instruction file at a given base path.
+* Prefers AGENTS.md over CLAUDE.md.
+*/
+function findInstructionFile(basePath, reader = fsInstructionReader) {
+	for (const filename of INSTRUCTION_FILES) {
+		const fullPath = join(basePath, filename);
+		if (reader.exists(fullPath)) return fullPath;
+	}
+	return null;
+}
+/**
+* Load all agent instruction files from global and project locations.
+* Returns an array of instruction sources, with global ones first.
+*
+* `projectReader` controls where project-scope content comes from (defaults to
+* the working tree). Global instructions read the operator machine's
+* filesystem, unless `skipGlobal` keeps them out entirely.
+*/
+function loadAgentInstructions(projectPath, configDirName = DEFAULT_CONFIG_DIR, projectReader = fsInstructionReader, { skipGlobal = false } = {}) {
+	const sources = [];
+	const home = homedir();
+	const projectLocations = PROJECT_LOCATIONS.map((loc) => loc === ".mastracode" ? configDirName : loc);
+	const globalLocations = skipGlobal ? [] : GLOBAL_LOCATIONS.map((loc) => {
+		if (loc === ".mastracode") return configDirName;
+		if (loc === ".config/mastracode") return ".config/" + configDirName.replace(/^\./, "");
+		return loc;
+	});
+	for (const location of globalLocations) {
+		const filePath = findInstructionFile(join(home, location));
+		if (filePath) try {
+			const content = readFileSync(filePath, "utf-8").trim();
+			if (content) {
+				sources.push({
+					path: filePath,
+					content,
+					scope: "global"
+				});
+				break;
+			}
+		} catch {}
+	}
+	for (const location of projectLocations) {
+		const filePath = findInstructionFile(location ? join(projectPath, location) : projectPath, projectReader);
+		if (filePath) try {
+			const content = projectReader.read(filePath).trim();
+			if (content) {
+				sources.push({
+					path: filePath,
+					content,
+					scope: "project",
+					...projectReader.ref ? { ref: projectReader.ref } : {}
+				});
+				break;
+			}
+		} catch {}
+	}
+	return sources;
+}
+function getStaticallyLoadedInstructionPaths(projectPath, configDirName = DEFAULT_CONFIG_DIR, projectReader) {
+	return loadAgentInstructions(projectPath, configDirName, projectReader).map((source) => normalize(source.path));
+}
+/** Heading the agent-instructions block is introduced by in the system prompt. */
+const AGENT_INSTRUCTIONS_HEADING = "# Agent Instructions";
+/**
+* Format a single instruction source as it appears in the system prompt.
+*
+* Exported so callers that attribute prompt cost per source (the `/context`
+* audit) measure the exact block that is sent rather than reconstructing it.
+*/
+function formatInstructionSource(source) {
+	return `<!-- ${source.scope === "global" ? "Global" : "Project"} instructions from ${source.ref ? `${source.path} (at ref ${source.ref})` : source.path} -->\n${source.content}`;
+}
+/**
+* Format loaded instructions into a string for the system prompt.
+*/
+function formatAgentInstructions(sources) {
+	if (sources.length === 0) return "";
+	const sections = sources.map(formatInstructionSource);
+	return `\n${AGENT_INSTRUCTIONS_HEADING}\n\n${sections.join("\n\n")}\n`;
+}
+//#endregion
+export { AGENT_INSTRUCTIONS_HEADING, createGitRefInstructionReader, createGitRefReminderReader, formatAgentInstructions, formatInstructionSource, getStaticallyLoadedInstructionPaths, loadAgentInstructions };
+
+//# sourceMappingURL=agent-instructions.js.map

package/dist/agents/prompts/agent-instructions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-instructions.js","names":[],"sources":["../../../src/agents/prompts/agent-instructions.ts"],"sourcesContent":["/**\n * Load project and global agent instruction files (AGENTS.md, CLAUDE.md).\n * Prefers AGENTS.md over CLAUDE.md when multiple exist at the same location.\n */\n\nimport { execFileSync } from 'node:child_process';\nimport { existsSync, readFileSync, statSync } from 'node:fs';\nimport { homedir } from 'node:os';\nimport { isAbsolute, join, normalize, relative, sep } from 'node:path';\nimport { DEFAULT_CONFIG_DIR } from '../../constants.js';\n\n// Filenames to check, in order of preference\nconst INSTRUCTION_FILES = ['AGENTS.md', 'CLAUDE.md'];\n\n// Locations to scan (relative to project root or home)\nconst PROJECT_LOCATIONS = [\n  '', // project root\n  '.claude',\n  '.mastracode',\n];\n\nconst GLOBAL_LOCATIONS = ['.claude', '.mastracode', '.config/claude', '.config/mastracode'];\n\nexport interface InstructionSource {\n  path: string;\n  content: string;\n  scope: 'global' | 'project';\n  /** Git ref the content was read from, when not read off the working tree. */\n  ref?: string;\n}\n\n/**\n * Reads project-scope instruction files. The default implementation reads the\n * working tree via `fs`; alternative readers can serve content from another\n * source (e.g. a trusted git ref) while keeping working-tree paths as the\n * addressing scheme.\n */\nexport interface InstructionFileReader {\n  exists(path: string): boolean;\n  read(path: string): string;\n  /** Git ref backing this reader, recorded on the loaded sources. */\n  ref?: string;\n}\n\nconst fsInstructionReader: InstructionFileReader = {\n  exists: path => existsSync(path),\n  read: path => readFileSync(path, 'utf-8'),\n};\n\n/**\n * Create a reader that serves instruction files from a git ref instead of the\n * working tree. Paths are still addressed as working-tree paths under\n * `projectPath`; content comes from `git show <ref>:<relpath>` so an untrusted\n * checkout (e.g. a PR branch under review) cannot influence what is loaded.\n * Tries `origin/<ref>` first (remote truth), then the local ref. Any git\n * failure (missing ref, missing file, no repo) reports the file as absent.\n */\nexport function createGitRefInstructionReader(projectPath: string, ref: string): InstructionFileReader {\n  const toRelative = (path: string): string | null => {\n    const rel = relative(projectPath, path);\n    if (!rel || rel.startsWith('..') || isAbsolute(rel)) return null;\n    return rel.split(sep).join('/');\n  };\n  const show = (path: string): string | null => {\n    const rel = toRelative(path);\n    if (rel === null) return null;\n    for (const candidate of [`origin/${ref}`, ref]) {\n      try {\n        return execFileSync('git', ['-C', projectPath, 'show', `${candidate}:${rel}`], {\n          encoding: 'utf-8',\n          stdio: ['ignore', 'pipe', 'ignore'],\n          maxBuffer: 1024 * 1024,\n        });\n      } catch {\n        // Ref or file missing at this candidate — try the next one.\n      }\n    }\n    return null;\n  };\n  return {\n    ref,\n    exists: path => show(path) !== null,\n    read: path => {\n      const content = show(path);\n      if (content === null) throw new Error(`Not found at ref ${ref}: ${path}`);\n      return content;\n    },\n  };\n}\n\n/**\n * Reader for the reactive reminder channel (AgentsMDInjector) that serves\n * paths under `projectPath` from a trusted git ref. Paths outside the project\n * fall back to the operator machine's filesystem (those are trusted); paths\n * inside the project are only ever resolved against the ref, never the\n * working tree, so an untrusted checkout cannot feed content in.\n */\nexport function createGitRefReminderReader(\n  projectPath: string,\n  ref: string,\n): {\n  pathExists: (path: string) => boolean;\n  isDirectory: (path: string) => boolean;\n  readFile: (path: string) => string;\n} {\n  const gitReader = createGitRefInstructionReader(projectPath, ref);\n  const toRelative = (path: string): string | null => {\n    const rel = relative(projectPath, normalize(path));\n    if (rel.startsWith('..') || isAbsolute(rel)) return null;\n    return rel.split(sep).join('/');\n  };\n  const objectType = (rel: string): string | null => {\n    if (rel === '') return 'tree'; // project root\n    for (const candidate of [`origin/${ref}`, ref]) {\n      try {\n        return execFileSync('git', ['-C', projectPath, 'cat-file', '-t', `${candidate}:${rel}`], {\n          encoding: 'utf-8',\n          stdio: ['ignore', 'pipe', 'ignore'],\n        }).trim();\n      } catch {\n        // Ref or object missing at this candidate — try the next one.\n      }\n    }\n    return null;\n  };\n  return {\n    pathExists: path => {\n      const rel = toRelative(path);\n      if (rel === null) return existsSync(path);\n      return objectType(rel) !== null;\n    },\n    isDirectory: path => {\n      const rel = toRelative(path);\n      if (rel === null) {\n        try {\n          return statSync(path).isDirectory();\n        } catch {\n          return false;\n        }\n      }\n      return objectType(rel) === 'tree';\n    },\n    readFile: path => {\n      const rel = toRelative(path);\n      if (rel === null) return readFileSync(path, 'utf-8');\n      return gitReader.read(path);\n    },\n  };\n}\n\n/**\n * Find the first existing instruction file at a given base path.\n * Prefers AGENTS.md over CLAUDE.md.\n */\nfunction findInstructionFile(basePath: string, reader: InstructionFileReader = fsInstructionReader): string | null {\n  for (const filename of INSTRUCTION_FILES) {\n    const fullPath = join(basePath, filename);\n    if (reader.exists(fullPath)) {\n      return fullPath;\n    }\n  }\n  return null;\n}\n\n/**\n * Load all agent instruction files from global and project locations.\n * Returns an array of instruction sources, with global ones first.\n *\n * `projectReader` controls where project-scope content comes from (defaults to\n * the working tree). Global instructions read the operator machine's\n * filesystem, unless `skipGlobal` keeps them out entirely.\n */\nexport function loadAgentInstructions(\n  projectPath: string,\n  configDirName = DEFAULT_CONFIG_DIR,\n  projectReader: InstructionFileReader = fsInstructionReader,\n  { skipGlobal = false }: { skipGlobal?: boolean } = {},\n): InstructionSource[] {\n  const sources: InstructionSource[] = [];\n  const home = homedir();\n\n  // Derive location arrays from the base constants, substituting the config dir name\n  const projectLocations = PROJECT_LOCATIONS.map(loc => (loc === '.mastracode' ? configDirName : loc));\n  const globalLocations = skipGlobal\n    ? []\n    : GLOBAL_LOCATIONS.map(loc => {\n        if (loc === '.mastracode') return configDirName;\n        // XDG-style path (~/.config/<name>): strip the leading dot since the\n        // .config/ prefix already signals a hidden/config directory.\n        if (loc === '.config/mastracode') return '.config/' + configDirName.replace(/^\\./, '');\n        return loc;\n      });\n\n  // Load global instructions first\n  for (const location of globalLocations) {\n    const basePath = join(home, location);\n    const filePath = findInstructionFile(basePath);\n    if (filePath) {\n      try {\n        const content = readFileSync(filePath, 'utf-8').trim();\n        if (content) {\n          sources.push({ path: filePath, content, scope: 'global' });\n          break; // Only use first found global instruction file\n        }\n      } catch {\n        // Skip unreadable files\n      }\n    }\n  }\n\n  // Load project instructions\n  for (const location of projectLocations) {\n    const basePath = location ? join(projectPath, location) : projectPath;\n    const filePath = findInstructionFile(basePath, projectReader);\n    if (filePath) {\n      try {\n        const content = projectReader.read(filePath).trim();\n        if (content) {\n          sources.push({\n            path: filePath,\n            content,\n            scope: 'project',\n            ...(projectReader.ref ? { ref: projectReader.ref } : {}),\n          });\n          break; // Only use first found project instruction file\n        }\n      } catch {\n        // Skip unreadable files\n      }\n    }\n  }\n\n  return sources;\n}\n\nexport function getStaticallyLoadedInstructionPaths(\n  projectPath: string,\n  configDirName = DEFAULT_CONFIG_DIR,\n  projectReader?: InstructionFileReader,\n): string[] {\n  return loadAgentInstructions(projectPath, configDirName, projectReader).map(source => normalize(source.path));\n}\n\n/** Heading the agent-instructions block is introduced by in the system prompt. */\nexport const AGENT_INSTRUCTIONS_HEADING = '# Agent Instructions';\n\n/**\n * Format a single instruction source as it appears in the system prompt.\n *\n * Exported so callers that attribute prompt cost per source (the `/context`\n * audit) measure the exact block that is sent rather than reconstructing it.\n */\nexport function formatInstructionSource(source: InstructionSource): string {\n  const label = source.scope === 'global' ? 'Global' : 'Project';\n  const origin = source.ref ? `${source.path} (at ref ${source.ref})` : source.path;\n  return `<!-- ${label} instructions from ${origin} -->\\n${source.content}`;\n}\n\n/**\n * Format loaded instructions into a string for the system prompt.\n */\nexport function formatAgentInstructions(sources: InstructionSource[]): string {\n  if (sources.length === 0) return '';\n\n  const sections = sources.map(formatInstructionSource);\n\n  return `\\n${AGENT_INSTRUCTIONS_HEADING}\\n\\n${sections.join('\\n\\n')}\\n`;\n}\n"],"mappings":";;;;;;;;;;AAYA,MAAM,oBAAoB,CAAC,aAAa,WAAW;AAGnD,MAAM,oBAAoB;CACxB;CACA;CACA;AACF;AAEA,MAAM,mBAAmB;CAAC;CAAW;CAAe;CAAkB;AAAoB;AAuB1F,MAAM,sBAA6C;CACjD,SAAQ,SAAQ,WAAW,IAAI;CAC/B,OAAM,SAAQ,aAAa,MAAM,OAAO;AAC1C;;;;;;;;;AAUA,SAAgB,8BAA8B,aAAqB,KAAoC;CACrG,MAAM,cAAc,SAAgC;EAClD,MAAM,MAAM,SAAS,aAAa,IAAI;EACtC,IAAI,CAAC,OAAO,IAAI,WAAW,IAAI,KAAK,WAAW,GAAG,GAAG,OAAO;EAC5D,OAAO,IAAI,MAAM,GAAG,CAAC,CAAC,KAAK,GAAG;CAChC;CACA,MAAM,QAAQ,SAAgC;EAC5C,MAAM,MAAM,WAAW,IAAI;EAC3B,IAAI,QAAQ,MAAM,OAAO;EACzB,KAAK,MAAM,aAAa,CAAC,UAAU,OAAO,GAAG,GAC3C,IAAI;GACF,OAAO,aAAa,OAAO;IAAC;IAAM;IAAa;IAAQ,GAAG,UAAU,GAAG;GAAK,GAAG;IAC7E,UAAU;IACV,OAAO;KAAC;KAAU;KAAQ;IAAQ;IAClC,WAAW,OAAO;GACpB,CAAC;EACH,QAAQ,CAER;EAEF,OAAO;CACT;CACA,OAAO;EACL;EACA,SAAQ,SAAQ,KAAK,IAAI,MAAM;EAC/B,OAAM,SAAQ;GACZ,MAAM,UAAU,KAAK,IAAI;GACzB,IAAI,YAAY,MAAM,MAAM,IAAI,MAAM,oBAAoB,IAAI,IAAI,MAAM;GACxE,OAAO;EACT;CACF;AACF;;;;;;;;AASA,SAAgB,2BACd,aACA,KAKA;CACA,MAAM,YAAY,8BAA8B,aAAa,GAAG;CAChE,MAAM,cAAc,SAAgC;EAClD,MAAM,MAAM,SAAS,aAAa,UAAU,IAAI,CAAC;EACjD,IAAI,IAAI,WAAW,IAAI,KAAK,WAAW,GAAG,GAAG,OAAO;EACpD,OAAO,IAAI,MAAM,GAAG,CAAC,CAAC,KAAK,GAAG;CAChC;CACA,MAAM,cAAc,QAA+B;EACjD,IAAI,QAAQ,IAAI,OAAO;EACvB,KAAK,MAAM,aAAa,CAAC,UAAU,OAAO,GAAG,GAC3C,IAAI;GACF,OAAO,aAAa,OAAO;IAAC;IAAM;IAAa;IAAY;IAAM,GAAG,UAAU,GAAG;GAAK,GAAG;IACvF,UAAU;IACV,OAAO;KAAC;KAAU;KAAQ;IAAQ;GACpC,CAAC,CAAC,CAAC,KAAK;EACV,QAAQ,CAER;EAEF,OAAO;CACT;CACA,OAAO;EACL,aAAY,SAAQ;GAClB,MAAM,MAAM,WAAW,IAAI;GAC3B,IAAI,QAAQ,MAAM,OAAO,WAAW,IAAI;GACxC,OAAO,WAAW,GAAG,MAAM;EAC7B;EACA,cAAa,SAAQ;GACnB,MAAM,MAAM,WAAW,IAAI;GAC3B,IAAI,QAAQ,MACV,IAAI;IACF,OAAO,SAAS,IAAI,CAAC,CAAC,YAAY;GACpC,QAAQ;IACN,OAAO;GACT;GAEF,OAAO,WAAW,GAAG,MAAM;EAC7B;EACA,WAAU,SAAQ;GAEhB,IADY,WAAW,IACjB,MAAM,MAAM,OAAO,aAAa,MAAM,OAAO;GACnD,OAAO,UAAU,KAAK,IAAI;EAC5B;CACF;AACF;;;;;AAMA,SAAS,oBAAoB,UAAkB,SAAgC,qBAAoC;CACjH,KAAK,MAAM,YAAY,mBAAmB;EACxC,MAAM,WAAW,KAAK,UAAU,QAAQ;EACxC,IAAI,OAAO,OAAO,QAAQ,GACxB,OAAO;CAEX;CACA,OAAO;AACT;;;;;;;;;AAUA,SAAgB,sBACd,aACA,gBAAgB,oBAChB,gBAAuC,qBACvC,EAAE,aAAa,UAAoC,CAAC,GAC/B;CACrB,MAAM,UAA+B,CAAC;CACtC,MAAM,OAAO,QAAQ;CAGrB,MAAM,mBAAmB,kBAAkB,KAAI,QAAQ,QAAQ,gBAAgB,gBAAgB,GAAI;CACnG,MAAM,kBAAkB,aACpB,CAAC,IACD,iBAAiB,KAAI,QAAO;EAC1B,IAAI,QAAQ,eAAe,OAAO;EAGlC,IAAI,QAAQ,sBAAsB,OAAO,aAAa,cAAc,QAAQ,OAAO,EAAE;EACrF,OAAO;CACT,CAAC;CAGL,KAAK,MAAM,YAAY,iBAAiB;EAEtC,MAAM,WAAW,oBADA,KAAK,MAAM,QACgB,CAAC;EAC7C,IAAI,UACF,IAAI;GACF,MAAM,UAAU,aAAa,UAAU,OAAO,CAAC,CAAC,KAAK;GACrD,IAAI,SAAS;IACX,QAAQ,KAAK;KAAE,MAAM;KAAU;KAAS,OAAO;IAAS,CAAC;IACzD;GACF;EACF,QAAQ,CAER;CAEJ;CAGA,KAAK,MAAM,YAAY,kBAAkB;EAEvC,MAAM,WAAW,oBADA,WAAW,KAAK,aAAa,QAAQ,IAAI,aACX,aAAa;EAC5D,IAAI,UACF,IAAI;GACF,MAAM,UAAU,cAAc,KAAK,QAAQ,CAAC,CAAC,KAAK;GAClD,IAAI,SAAS;IACX,QAAQ,KAAK;KACX,MAAM;KACN;KACA,OAAO;KACP,GAAI,cAAc,MAAM,EAAE,KAAK,cAAc,IAAI,IAAI,CAAC;IACxD,CAAC;IACD;GACF;EACF,QAAQ,CAER;CAEJ;CAEA,OAAO;AACT;AAEA,SAAgB,oCACd,aACA,gBAAgB,oBAChB,eACU;CACV,OAAO,sBAAsB,aAAa,eAAe,aAAa,CAAC,CAAC,KAAI,WAAU,UAAU,OAAO,IAAI,CAAC;AAC9G;;AAGA,MAAa,6BAA6B;;;;;;;AAQ1C,SAAgB,wBAAwB,QAAmC;CAGzE,OAAO,QAFO,OAAO,UAAU,WAAW,WAAW,UAEhC,qBADN,OAAO,MAAM,GAAG,OAAO,KAAK,WAAW,OAAO,IAAI,KAAK,OAAO,KAC5B,QAAQ,OAAO;AAClE;;;;AAKA,SAAgB,wBAAwB,SAAsC;CAC5E,IAAI,QAAQ,WAAW,GAAG,OAAO;CAEjC,MAAM,WAAW,QAAQ,IAAI,uBAAuB;CAEpD,OAAO,KAAK,2BAA2B,MAAM,SAAS,KAAK,MAAM,EAAE;AACrE"}

package/dist/agents/prompts/build.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Build mode prompt — full tool access, make changes and verify.
+ */
+import type { PromptContext } from './index.js';
+/**
+ * Dynamic build mode prompt function.
+ * When an approved plan exists in state, prepends it so the agent
+ * knows exactly what to implement.
+ */
+export declare function buildModePromptFn(ctx: PromptContext): string;
+export declare const buildModePrompt = "\n# Build Mode\n\nYou are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.\n\n## Working Style\n\n**For simple tasks** (typo fixes, small edits, single-file changes):\n- Just do it. No need to explain your plan first.\n\n**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):\n- Use the available task-management tools to create and update your task list\n- Work on ONE step at a time \u2014 complete it and verify it works before moving on\n- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user\n\n## The Implementation Loop\n\nFor each change you make:\n\n1. **Understand** \u2014 Read the relevant code. Check how similar things are done elsewhere.\n2. **Implement** \u2014 Make the change. Follow existing patterns and conventions.\n3. **Verify** \u2014 Test that it works. Don't assume \u2014 actually run it.\n4. **Prove** \u2014 Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.\n5. **Clean up** \u2014 Ensure no broken code, no debug statements, no half-done features.\n\nOnly move to the next change after the current one is verified and proved to be working.\n\n## Verification is Required\n\nBefore considering any task complete:\n- Run relevant tests (check package.json for test scripts)\n- For TypeScript, run `tsc --noEmit` to catch type errors\n- If there are no automated tests, manually verify the behavior works as expected\n- Confirm the result makes sense in the codebase and improves the requested behavior\n- Use available task-checking tools to ensure all tracked tasks are done\n\n**Don't mark something as done until you've verified and proved it actually works.**\n\n## Error Recovery\n\nWhen something breaks:\n1. Read the full error output carefully \u2014 don't guess\n2. Find the root cause, not just the symptom\n3. Fix it properly \u2014 no casts or suppressions to hide errors\n4. Re-run to confirm the fix\n5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option\n\n## Git in Build Mode\n\n- Before committing, verify the code compiles and passes lint\n- Use descriptive branch names: `feat/...`, `fix/...`, `refactor/...`\n";
+//# sourceMappingURL=build.d.ts.map

package/dist/agents/prompts/build.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"build.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/build.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,YAAY,CAAC;AAEhD;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CAiB5D;AAED,eAAO,MAAM,eAAe,00EAmD3B,CAAC"}

package/dist/agents/prompts/build.js

@@ -0,0 +1,76 @@
+//#region src/agents/prompts/build.ts
+/**
+* Dynamic build mode prompt function.
+* When an approved plan exists in state, prepends it so the agent
+* knows exactly what to implement.
+*/
+function buildModePromptFn(ctx) {
+	if (ctx.activePlan) return `# Approved Plan
+
+**${ctx.activePlan.title}**
+
+${ctx.activePlan.plan}
+
+---
+
+Implement the approved plan above. Follow the steps in order and verify each step works before moving on.
+
+` + buildModePrompt;
+	return buildModePrompt;
+}
+const buildModePrompt = `
+# Build Mode
+
+You are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.
+
+## Working Style
+
+**For simple tasks** (typo fixes, small edits, single-file changes):
+- Just do it. No need to explain your plan first.
+
+**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):
+- Use the available task-management tools to create and update your task list
+- Work on ONE step at a time — complete it and verify it works before moving on
+- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user
+
+## The Implementation Loop
+
+For each change you make:
+
+1. **Understand** — Read the relevant code. Check how similar things are done elsewhere.
+2. **Implement** — Make the change. Follow existing patterns and conventions.
+3. **Verify** — Test that it works. Don't assume — actually run it.
+4. **Prove** — Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.
+5. **Clean up** — Ensure no broken code, no debug statements, no half-done features.
+
+Only move to the next change after the current one is verified and proved to be working.
+
+## Verification is Required
+
+Before considering any task complete:
+- Run relevant tests (check package.json for test scripts)
+- For TypeScript, run \`tsc --noEmit\` to catch type errors
+- If there are no automated tests, manually verify the behavior works as expected
+- Confirm the result makes sense in the codebase and improves the requested behavior
+- Use available task-checking tools to ensure all tracked tasks are done
+
+**Don't mark something as done until you've verified and proved it actually works.**
+
+## Error Recovery
+
+When something breaks:
+1. Read the full error output carefully — don't guess
+2. Find the root cause, not just the symptom
+3. Fix it properly — no casts or suppressions to hide errors
+4. Re-run to confirm the fix
+5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option
+
+## Git in Build Mode
+
+- Before committing, verify the code compiles and passes lint
+- Use descriptive branch names: \`feat/...\`, \`fix/...\`, \`refactor/...\`
+`;
+//#endregion
+export { buildModePrompt, buildModePromptFn };
+
+//# sourceMappingURL=build.js.map

package/dist/agents/prompts/build.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"build.js","names":[],"sources":["../../../src/agents/prompts/build.ts"],"sourcesContent":["/**\n * Build mode prompt — full tool access, make changes and verify.\n */\n\nimport type { PromptContext } from './index.js';\n\n/**\n * Dynamic build mode prompt function.\n * When an approved plan exists in state, prepends it so the agent\n * knows exactly what to implement.\n */\nexport function buildModePromptFn(ctx: PromptContext): string {\n  if (ctx.activePlan) {\n    return (\n      `# Approved Plan\n\n**${ctx.activePlan.title}**\n\n${ctx.activePlan.plan}\n\n---\n\nImplement the approved plan above. Follow the steps in order and verify each step works before moving on.\n\n` + buildModePrompt\n    );\n  }\n  return buildModePrompt;\n}\n\nexport const buildModePrompt = `\n# Build Mode\n\nYou are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.\n\n## Working Style\n\n**For simple tasks** (typo fixes, small edits, single-file changes):\n- Just do it. No need to explain your plan first.\n\n**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):\n- Use the available task-management tools to create and update your task list\n- Work on ONE step at a time — complete it and verify it works before moving on\n- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user\n\n## The Implementation Loop\n\nFor each change you make:\n\n1. **Understand** — Read the relevant code. Check how similar things are done elsewhere.\n2. **Implement** — Make the change. Follow existing patterns and conventions.\n3. **Verify** — Test that it works. Don't assume — actually run it.\n4. **Prove** — Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.\n5. **Clean up** — Ensure no broken code, no debug statements, no half-done features.\n\nOnly move to the next change after the current one is verified and proved to be working.\n\n## Verification is Required\n\nBefore considering any task complete:\n- Run relevant tests (check package.json for test scripts)\n- For TypeScript, run \\`tsc --noEmit\\` to catch type errors\n- If there are no automated tests, manually verify the behavior works as expected\n- Confirm the result makes sense in the codebase and improves the requested behavior\n- Use available task-checking tools to ensure all tracked tasks are done\n\n**Don't mark something as done until you've verified and proved it actually works.**\n\n## Error Recovery\n\nWhen something breaks:\n1. Read the full error output carefully — don't guess\n2. Find the root cause, not just the symptom\n3. Fix it properly — no casts or suppressions to hide errors\n4. Re-run to confirm the fix\n5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option\n\n## Git in Build Mode\n\n- Before committing, verify the code compiles and passes lint\n- Use descriptive branch names: \\`feat/...\\`, \\`fix/...\\`, \\`refactor/...\\`\n`;\n"],"mappings":";;;;;;AAWA,SAAgB,kBAAkB,KAA4B;CAC5D,IAAI,IAAI,YACN,OACE;;IAEF,IAAI,WAAW,MAAM;;EAEvB,IAAI,WAAW,KAAK;;;;;;IAMlB;CAGF,OAAO;AACT;AAEA,MAAa,kBAAkB"}

package/dist/agents/prompts/fast.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Fast mode prompt — quick answers and small edits, minimal overhead.
+ */
+export declare const fastModePrompt = "\n# Fast Mode\n\nYou are in FAST mode. Optimize for speed and brevity.\n\n## Rules\n- Keep responses short. Under 200 words unless the task genuinely requires more.\n- Skip planning. Just do the task directly.\n- For questions: give the direct answer, not a tutorial.\n- For edits: make the change, show what you did, move on.\n- Don't explore the codebase more than necessary for the immediate task.\n\n## When to Use Tools vs. Just Answer\n- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.\n- If the user asks about THIS project's code, use tools to look it up \u2014 don't guess.\n- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.\n- One tool call to read + one to edit is ideal. Minimize round trips.\n";
+//# sourceMappingURL=fast.d.ts.map

package/dist/agents/prompts/fast.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fast.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/fast.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,eAAO,MAAM,cAAc,6zBAiB1B,CAAC"}

package/dist/agents/prompts/fast.js

@@ -0,0 +1,26 @@
+//#region src/agents/prompts/fast.ts
+/**
+* Fast mode prompt — quick answers and small edits, minimal overhead.
+*/
+const fastModePrompt = `
+# Fast Mode
+
+You are in FAST mode. Optimize for speed and brevity.
+
+## Rules
+- Keep responses short. Under 200 words unless the task genuinely requires more.
+- Skip planning. Just do the task directly.
+- For questions: give the direct answer, not a tutorial.
+- For edits: make the change, show what you did, move on.
+- Don't explore the codebase more than necessary for the immediate task.
+
+## When to Use Tools vs. Just Answer
+- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.
+- If the user asks about THIS project's code, use tools to look it up — don't guess.
+- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.
+- One tool call to read + one to edit is ideal. Minimize round trips.
+`;
+//#endregion
+export { fastModePrompt };
+
+//# sourceMappingURL=fast.js.map

package/dist/agents/prompts/fast.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"fast.js","names":[],"sources":["../../../src/agents/prompts/fast.ts"],"sourcesContent":["/**\n * Fast mode prompt — quick answers and small edits, minimal overhead.\n */\n\nexport const fastModePrompt = `\n# Fast Mode\n\nYou are in FAST mode. Optimize for speed and brevity.\n\n## Rules\n- Keep responses short. Under 200 words unless the task genuinely requires more.\n- Skip planning. Just do the task directly.\n- For questions: give the direct answer, not a tutorial.\n- For edits: make the change, show what you did, move on.\n- Don't explore the codebase more than necessary for the immediate task.\n\n## When to Use Tools vs. Just Answer\n- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.\n- If the user asks about THIS project's code, use tools to look it up — don't guess.\n- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.\n- One tool call to read + one to edit is ideal. Minimize round trips.\n`;\n"],"mappings":";;;;AAIA,MAAa,iBAAiB"}

package/dist/agents/prompts/index.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Prompt system — exports the prompt builder and mode-specific prompts.
+ */
+export { buildModePrompt, buildModePromptFn } from './build.js';
+export { planModePrompt } from './plan.js';
+export { fastModePrompt } from './fast.js';
+import type { PromptContext as BasePromptContext } from '@mastra/core/coding-agent';
+export interface PromptContext extends Omit<BasePromptContext, 'toolGuidance'> {
+    modeId: string;
+    state?: any;
+    /** The subconscious knowledge tools are registered on the agent. */
+    hasSubconscious?: boolean;
+    hostInstructions?: string;
+    currentDate: string;
+    workingDir: string;
+}
+/**
+ * One labeled piece of the assembled system prompt.
+ *
+ * The system prompt is a single string by the time it reaches the model, which
+ * makes it impossible to say which configuration source is responsible for
+ * which share of the context window. Building it as labeled sections and
+ * joining them at the end keeps that attribution available to the `/context`
+ * audit while guaranteeing the audit measures the exact text that is sent —
+ * a parallel "describe the prompt" path would drift and report numbers for a
+ * prompt that is no longer assembled this way.
+ */
+export interface PromptSection {
+    /** Stable identifier, unique within a single build. */
+    id: string;
+    /** Human-readable label for display. */
+    label: string;
+    /** Optional provenance (e.g. the instruction file path). */
+    detail?: string;
+    /** The exact text contributed to the prompt. */
+    content: string;
+}
+/** Join prompt sections into the final system prompt string. */
+export declare function joinPromptSections(sections: PromptSection[]): string;
+/**
+ * Build the full system prompt for a given mode and context.
+ * Combines the base prompt with mode-specific instructions.
+ */
+export declare function buildFullPrompt(ctx: PromptContext): string;
+/**
+ * Build the system prompt as labeled sections. `buildFullPrompt` is the join of
+ * these, so the two can never disagree about what the model receives.
+ */
+export declare function buildFullPromptSections(ctx: PromptContext): PromptSection[];
+//# sourceMappingURL=index.d.ts.map

package/dist/agents/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,eAAe,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAChE,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAC3C,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAG3C,OAAO,KAAK,EAAE,aAAa,IAAI,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AAkBpF,MAAM,WAAW,aAAc,SAAQ,IAAI,CAAC,iBAAiB,EAAE,cAAc,CAAC;IAC5E,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,GAAG,CAAC;IACZ,oEAAoE;IACpE,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;CACpB;AAQD;;;;;;;;;;GAUG;AACH,MAAM,WAAW,aAAa;IAC5B,uDAAuD;IACvD,EAAE,EAAE,MAAM,CAAC;IACX,wCAAwC;IACxC,KAAK,EAAE,MAAM,CAAC;IACd,4DAA4D;IAC5D,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,gDAAgD;IAChD,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,gEAAgE;AAChE,wBAAgB,kBAAkB,CAAC,QAAQ,EAAE,aAAa,EAAE,GAAG,MAAM,CAKpE;AAED;;;GAGG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CAE1D;AAED;;;GAGG;AACH,wBAAgB,uBAAuB,CAAC,GAAG,EAAE,aAAa,GAAG,aAAa,EAAE,CAkH3E"}