@mastra/code-sdk 1.0.3-alpha.0 → 1.1.0-alpha.2

package/dist/agents/prompts/tool-guidance.js

@@ -1,114 +1,97 @@
 import { MC_TOOLS } from "../../tool-names.js";
+//#region src/agents/prompts/tool-guidance.ts
+/**
+* Mode-specific tool behavioral guidance.
+* Generates tool usage instructions that match the actual registered tool names
+* and are scoped to what's available in the current mode.
+*/
 function buildToolGuidance(modeId, options = {}) {
-  const denied = options.deniedTools ?? /* @__PURE__ */ new Set();
-  const sections = [];
-  sections.push(`# Tool Usage Rules
+	const denied = options.deniedTools ?? /* @__PURE__ */ new Set();
+	const sections = [];
+	sections.push(`# Tool Usage Rules
 
-IMPORTANT: You can ONLY call tools by their exact registered names listed below. Shell commands like \`git\`, \`npm\`, \`ls\`, etc. are NOT tools \u2014 they must be run via the \`execute_command\` tool.
+IMPORTANT: You can ONLY call tools by their exact registered names listed below. Shell commands like \`git\`, \`npm\`, \`ls\`, etc. are NOT tools — they must be run via the \`execute_command\` tool.
 
 You have access to the following tools. Use the RIGHT tool for the job:`);
-  const readTools = [];
-  if (!denied.has(MC_TOOLS.VIEW)) {
-    readTools.push(`
-**${MC_TOOLS.VIEW}** \u2014 Read file contents
+	const readTools = [];
+	if (!denied.has(MC_TOOLS.VIEW)) readTools.push(`
+**${MC_TOOLS.VIEW}** — Read file contents
 - Use this to read files before editing them. NEVER propose changes to code you haven't read.
 - Use \`offset\` (1-indexed start line) and \`limit\` (number of lines) for large files.
 - Example: Read lines 50-100: \`{ path: "src/big-file.ts", offset: 50, limit: 51 }\`
 - To list directories, use \`${MC_TOOLS.FIND_FILES}\` instead.`);
-  }
-  if (!denied.has(MC_TOOLS.SEARCH_CONTENT)) {
-    readTools.push(`
-**${MC_TOOLS.SEARCH_CONTENT}** \u2014 Search file contents using regex
+	if (!denied.has(MC_TOOLS.SEARCH_CONTENT)) readTools.push(`
+**${MC_TOOLS.SEARCH_CONTENT}** — Search file contents using regex
 - Preferred for content search (finding functions, variables, error messages, imports, etc.)
 - Use \`path\` to filter by directory or glob pattern. Supports \`contextLines\`, \`caseSensitive\`, and \`maxCount\`.
 - Example: Find a function: \`{ pattern: "function handleSubmit", path: "**/*.ts" }\`
 - Example: Find imports: \`{ pattern: "from ['\\"\\]express['\\"\\]", path: "**/*.ts" }\`
 - Respects .gitignore by default.`);
-  }
-  if (!denied.has(MC_TOOLS.FIND_FILES)) {
-    readTools.push(`
-**${MC_TOOLS.FIND_FILES}** \u2014 List files and directories as a tree
+	if (!denied.has(MC_TOOLS.FIND_FILES)) readTools.push(`
+**${MC_TOOLS.FIND_FILES}** — List files and directories as a tree
 - Preferred for exploring project structure and finding files by pattern.
 - Returns tree-style output. Respects .gitignore by default.
 - Example: List project root: \`{ path: "./" }\`
 - Example: Find test files: \`{ path: "./src", pattern: "**/*.test.ts" }\`
 - Example: Find config files: \`{ pattern: "*.config.{js,ts,json}" }\``);
-  }
-  if (!denied.has(MC_TOOLS.EXECUTE_COMMAND)) {
-    readTools.push(`
-**${MC_TOOLS.EXECUTE_COMMAND}** \u2014 Run shell commands
+	if (!denied.has(MC_TOOLS.EXECUTE_COMMAND)) readTools.push(`
+**${MC_TOOLS.EXECUTE_COMMAND}** — Run shell commands
 - Use for: git, npm/pnpm, docker, build tools, test runners, and other terminal operations.
 - Prefer dedicated tools for: file reading (${MC_TOOLS.VIEW}), file search (${MC_TOOLS.SEARCH_CONTENT}/${MC_TOOLS.FIND_FILES}), file editing (${MC_TOOLS.STRING_REPLACE_LSP}/${MC_TOOLS.WRITE_FILE}).
 - Commands have a 30-second default timeout. Use \`timeout\` for longer commands, \`cwd\` for working directory.
-- Use the \`tail\` parameter or pipe to \`| tail -N\` to limit output \u2014 the full output streams to the user, only the tail is returned to you. If you're building any kind of package you should be tailing.
+- Use the \`tail\` parameter or pipe to \`| tail -N\` to limit output — the full output streams to the user, only the tail is returned to you. If you're building any kind of package you should be tailing.
 - Good: Run independent commands in parallel when possible.
-- Bad: Running \`cat file.txt\` \u2014 use the ${MC_TOOLS.VIEW} tool instead.`);
-  }
-  if (!denied.has(MC_TOOLS.LSP_INSPECT)) {
-    readTools.push(`
-**${MC_TOOLS.LSP_INSPECT}** \u2014 Inspect code using Language Server Protocol
+- Bad: Running \`cat file.txt\` — use the ${MC_TOOLS.VIEW} tool instead.`);
+	if (!denied.has(MC_TOOLS.LSP_INSPECT)) readTools.push(`
+**${MC_TOOLS.LSP_INSPECT}** — Inspect code using Language Server Protocol
 - Use this for type information, hover docs, go-to-definition, and finding implementations for a symbol.
 - Best when you already know the file and line and need semantic code intelligence rather than raw file contents.
 - Input: \`path\` (absolute file path), \`line\` (1-indexed line number), \`match\` (the exact line content with exactly one \`<<<\` cursor marker).
 - Output includes: \`hover\`, \`definition\` (compact location with preview), and \`implementation\` (compact usage/implementation locations).
-- Example: \`{ path: "/abs/path/src/foo.ts", line: 10, match: "const foo = <<<bar()" }\` \u2014 inspect the symbol at the \`<<<\` position.
+- Example: \`{ path: "/abs/path/src/foo.ts", line: 10, match: "const foo = <<<bar()" }\` — inspect the symbol at the \`<<<\` position.
 - Use \`${MC_TOOLS.VIEW}\` when you need to read the implementation or surrounding code.
 - Use \`${MC_TOOLS.SEARCH_CONTENT}\` or \`${MC_TOOLS.FIND_FILES}\` first if you do not yet know where the symbol is.`);
-  }
-  if (!denied.has(MC_TOOLS.NOTIFICATION_INBOX)) {
-    readTools.push(`
-**${MC_TOOLS.NOTIFICATION_INBOX}** \u2014 Inspect and manage notification inbox records
+	if (!denied.has(MC_TOOLS.NOTIFICATION_INBOX)) readTools.push(`
+**${MC_TOOLS.NOTIFICATION_INBOX}** — Inspect and manage notification inbox records
 - Use this when a \`<notification-summary>\` says pending notifications exist.
 - Use \`{ "action": "list", "status": "pending" }\` or \`{ "action": "search", "query": "..." }\` to find notification records for the current thread.
 - Use \`read\` to deliver unread notification signals into the chat and mark them seen; the tool result summarizes the count instead of exposing notification contents.
 - Use \`dismiss\` or \`archive\` only when the user asks or the notification is no longer relevant.`);
-  }
-  if (readTools.length > 0) {
-    sections.push(readTools.join("\n"));
-  }
-  if (modeId !== "plan") {
-    const writeTools = [];
-    if (!denied.has(MC_TOOLS.STRING_REPLACE_LSP)) {
-      writeTools.push(`
-**${MC_TOOLS.STRING_REPLACE_LSP}** \u2014 Edit files by replacing exact text
+	if (readTools.length > 0) sections.push(readTools.join("\n"));
+	if (modeId !== "plan") {
+		const writeTools = [];
+		if (!denied.has(MC_TOOLS.STRING_REPLACE_LSP)) writeTools.push(`
+**${MC_TOOLS.STRING_REPLACE_LSP}** — Edit files by replacing exact text
 - You MUST read a file with \`${MC_TOOLS.VIEW}\` before editing it.
 - \`old_string\` must be an exact match of existing text in the file.
 - Provide enough surrounding context in \`old_string\` to make it unique.
 - Use \`replace_all: true\` to replace all occurrences (default: false, requires unique match).
 - For creating new files, use \`${MC_TOOLS.WRITE_FILE}\` instead.
 - Good: Include 2-3 lines of surrounding context to ensure uniqueness.
-- Bad: Using just \`return true;\` \u2014 too common, will match multiple places.`);
-    }
-    if (!denied.has(MC_TOOLS.WRITE_FILE)) {
-      writeTools.push(`
-**${MC_TOOLS.WRITE_FILE}** \u2014 Create new files or overwrite existing ones
+- Bad: Using just \`return true;\` — too common, will match multiple places.`);
+		if (!denied.has(MC_TOOLS.WRITE_FILE)) writeTools.push(`
+**${MC_TOOLS.WRITE_FILE}** — Create new files or overwrite existing ones
 - Use this to create new files.
 - If overwriting an existing file, you MUST have read it first with \`${MC_TOOLS.VIEW}\`.
 - Prefer editing existing files over creating new ones.`);
-    }
-    if (writeTools.length > 0) {
-      sections.push(writeTools.join("\n"));
-    }
-  }
-  if (options.hasWebSearch) {
-    const webTools = [];
-    if (!denied.has("web_search")) webTools.push("**web_search**");
-    if (!denied.has("web_extract")) webTools.push("**web_extract**");
-    if (webTools.length > 0) {
-      sections.push(`
-${webTools.join(" / ")} \u2014 Search the web / extract page content
+		if (writeTools.length > 0) sections.push(writeTools.join("\n"));
+	}
+	if (options.hasWebSearch) {
+		const webTools = [];
+		if (!denied.has("web_search")) webTools.push("**web_search**");
+		if (!denied.has("web_extract")) webTools.push("**web_extract**");
+		if (webTools.length > 0) sections.push(`
+${webTools.join(" / ")} — Search the web / extract page content
 - Use for looking up documentation, error messages, package APIs.`);
-    }
-  }
-  const taskTools = [];
-  const canUpdateTask = !denied.has("task_update");
-  const canCompleteTask = !denied.has("task_complete");
-  const canCheckTasks = !denied.has("task_check");
-  const canWriteTasks = !denied.has("task_write");
-  const patchToolGuidance = canUpdateTask && canCompleteTask ? "- Prefer task_update or task_complete when changing one existing task." : canUpdateTask ? "- Prefer task_update when changing one existing task." : canCompleteTask ? "- Prefer task_complete when marking one existing task completed." : "- Use task_write with the full task list when changing existing tasks.";
-  if (canWriteTasks) {
-    taskTools.push(`
-**task_write** \u2014 Track tasks for complex multi-step work
+	}
+	const taskTools = [];
+	const canUpdateTask = !denied.has("task_update");
+	const canCompleteTask = !denied.has("task_complete");
+	const canCheckTasks = !denied.has("task_check");
+	const canWriteTasks = !denied.has("task_write");
+	const patchToolGuidance = canUpdateTask && canCompleteTask ? "- Prefer task_update or task_complete when changing one existing task." : canUpdateTask ? "- Prefer task_update when changing one existing task." : canCompleteTask ? "- Prefer task_complete when marking one existing task completed." : "- Use task_write with the full task list when changing existing tasks.";
+	if (canWriteTasks) taskTools.push(`
+**task_write** — Track tasks for complex multi-step work
 - Use when a task requires 3 or more distinct steps or actions.
 - Use task_write to create the initial task list or replace the whole list after replanning.
 - Each task has: id (stable identifier), content (imperative form), status (pending, in_progress, or completed), activeForm (present continuous form shown during execution).
@@ -116,66 +99,51 @@ ${webTools.join(" / ")} \u2014 Search the web / extract page content
 ${patchToolGuidance}
 - Mark tasks \`in_progress\` BEFORE starting work. Only ONE task should be \`in_progress\` at a time.
 - Mark tasks \`completed\` IMMEDIATELY after finishing each task. Do not batch completions.`);
-  }
-  if (canUpdateTask) {
-    taskTools.push(`
-**task_update** \u2014 Patch one tracked task by ID
+	if (canUpdateTask) taskTools.push(`
+**task_update** — Patch one tracked task by ID
 - Use this for targeted changes to one existing task.
 - Provide the task ID and only the fields that changed: content, status, or activeForm.`);
-  }
-  if (canCompleteTask) {
-    const idSource = canCheckTasks ? "Use task_check if you need the current IDs before completing a task." : canWriteTasks ? "Use IDs returned by task_write." : "Use only task IDs already visible in the current task list.";
-    taskTools.push(`
-**task_complete** \u2014 Mark one tracked task completed by ID
+	if (canCompleteTask) {
+		const idSource = canCheckTasks ? "Use task_check if you need the current IDs before completing a task." : canWriteTasks ? "Use IDs returned by task_write." : "Use only task IDs already visible in the current task list.";
+		taskTools.push(`
+**task_complete** — Mark one tracked task completed by ID
 - Use this immediately after finishing a tracked task.
 - ${idSource}`);
-  }
-  if (canCheckTasks) {
-    taskTools.push(`
-**task_check** \u2014 Check completion status of tasks
+	}
+	if (canCheckTasks) taskTools.push(`
+**task_check** — Check completion status of tasks
 - Use this BEFORE finishing tracked work to verify all tasks are completed.
 - Returns a readable status summary plus structured fields: tasks, summary, incompleteTasks, and isError.
 - summary includes total, completed, inProgress, pending, incomplete, hasTasks, and allCompleted.
 - Use summary.allCompleted to decide whether tracked work is complete; if summary.hasTasks is false, no task list is currently tracked.
 - If any tasks remain incomplete, continue working on them.
 - IMPORTANT: Always check task completion before ending work on a complex task.`);
-  }
-  if (!denied.has("ask_user")) {
-    taskTools.push(`
-**ask_user** \u2014 Ask the user a structured question
+	if (!denied.has("ask_user")) taskTools.push(`
+**ask_user** — Ask the user a structured question
 - Use when you need clarification, want to validate assumptions, or need the user to make a decision.
 - Provide clear, specific questions. End with a question mark.
 - Include options (2-4 choices) for structured decisions. Omit options for open-ended questions.
-- Don't use this for simple yes/no \u2014 just ask in your text response.`);
-  }
-  if (taskTools.length > 0) {
-    sections.push(taskTools.join("\n"));
-  }
-  if (modeId === "plan" && !denied.has("submit_plan")) {
-    sections.push(`
-**submit_plan** \u2014 Submit a completed implementation plan for user review
-- Call this tool when your plan is complete. Do NOT just describe your plan in text \u2014 you MUST call this tool.
+- Don't use this for simple yes/no — just ask in your text response.`);
+	if (taskTools.length > 0) sections.push(taskTools.join("\n"));
+	if (modeId === "plan" && !denied.has("submit_plan")) sections.push(`
+**submit_plan** — Submit a completed implementation plan for user review
+- Call this tool when your plan is complete. Do NOT just describe your plan in text — you MUST call this tool.
 - The plan will be rendered as markdown and the user can approve, reject, or request changes.
 - On approval, the system automatically switches to the default mode so you can implement.
-- Takes one argument: \`path\` (the plan markdown file you wrote under \`.mastracode/plans/\`). Do NOT pass the plan body \u2014 it lives in the file.`);
-  }
-  if (modeId === "plan") {
-    sections.push(`
-**Plan file access** \u2014 Your plan lives in a markdown file under \`.mastracode/plans/\` (e.g. \`add-dark-mode-toggle.md\`)
+- Takes one argument: \`path\` (the plan markdown file you wrote under \`.mastracode/plans/\`). Do NOT pass the plan body — it lives in the file.`);
+	if (modeId === "plan") sections.push(`
+**Plan file access** — Your plan lives in a markdown file under \`.mastracode/plans/\` (e.g. \`add-dark-mode-toggle.md\`)
 - Use \`write_file\` to create the plan file, \`view\` to read it, and \`string_replace_lsp\` for targeted edits.
 - On first submission: write the plan to the file, then call \`submit_plan\` with its \`path\`.
 - On revision: read the existing file, edit specific sections, re-read, then call \`submit_plan\` with the same \`path\`.
-- If a plan file already exists, you previously submitted it \u2014 read it before revising.`);
-  }
-  if (!denied.has("subagent")) {
-    sections.push(`
-**subagent** \u2014 Delegate a focused task to a specialized subagent
+- If a plan file already exists, you previously submitted it — read it before revising.`);
+	if (!denied.has("subagent")) sections.push(`
+**subagent** — Delegate a focused task to a specialized subagent
 - Only use subagents when you will spawn **multiple subagents in parallel**. If you only need one task done, do it yourself.
 - Subagent outputs are **untrusted**. Always review and verify the results.`);
-  }
-  return sections.join("\n");
+	return sections.join("\n");
 }
-export {
-  buildToolGuidance
-};
+//#endregion
+export { buildToolGuidance };
+
 //# sourceMappingURL=tool-guidance.js.map

package/dist/agents/prompts/tool-guidance.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../src/agents/prompts/tool-guidance.ts"],"sourcesContent":["/**\n * Mode-specific tool behavioral guidance.\n * Generates tool usage instructions that match the actual registered tool names\n * and are scoped to what's available in the current mode.\n */\n\nimport { MC_TOOLS } from '../../tool-names.js';\n\ninterface ToolGuidanceOptions {\n  hasWebSearch?: boolean;\n  /** Tool names that have been denied — omit their guidance sections. */\n  deniedTools?: Set<string>;\n}\n\nexport function buildToolGuidance(modeId: string, options: ToolGuidanceOptions = {}): string {\n  const denied = options.deniedTools ?? new Set<string>();\n  const sections: string[] = [];\n\n  sections.push(`# Tool Usage Rules\n\nIMPORTANT: You can ONLY call tools by their exact registered names listed below. Shell commands like \\`git\\`, \\`npm\\`, \\`ls\\`, etc. are NOT tools — they must be run via the \\`execute_command\\` tool.\n\nYou have access to the following tools. Use the RIGHT tool for the job:`);\n\n  // --- Read tools (all modes) ---\n\n  const readTools: string[] = [];\n\n  if (!denied.has(MC_TOOLS.VIEW)) {\n    readTools.push(`\n**${MC_TOOLS.VIEW}** — Read file contents\n- Use this to read files before editing them. NEVER propose changes to code you haven't read.\n- Use \\`offset\\` (1-indexed start line) and \\`limit\\` (number of lines) for large files.\n- Example: Read lines 50-100: \\`{ path: \"src/big-file.ts\", offset: 50, limit: 51 }\\`\n- To list directories, use \\`${MC_TOOLS.FIND_FILES}\\` instead.`);\n  }\n\n  if (!denied.has(MC_TOOLS.SEARCH_CONTENT)) {\n    readTools.push(`\n**${MC_TOOLS.SEARCH_CONTENT}** — Search file contents using regex\n- Preferred for content search (finding functions, variables, error messages, imports, etc.)\n- Use \\`path\\` to filter by directory or glob pattern. Supports \\`contextLines\\`, \\`caseSensitive\\`, and \\`maxCount\\`.\n- Example: Find a function: \\`{ pattern: \"function handleSubmit\", path: \"**/*.ts\" }\\`\n- Example: Find imports: \\`{ pattern: \"from ['\\\\\"\\\\]express['\\\\\"\\\\]\", path: \"**/*.ts\" }\\`\n- Respects .gitignore by default.`);\n  }\n\n  if (!denied.has(MC_TOOLS.FIND_FILES)) {\n    readTools.push(`\n**${MC_TOOLS.FIND_FILES}** — List files and directories as a tree\n- Preferred for exploring project structure and finding files by pattern.\n- Returns tree-style output. Respects .gitignore by default.\n- Example: List project root: \\`{ path: \"./\" }\\`\n- Example: Find test files: \\`{ path: \"./src\", pattern: \"**/*.test.ts\" }\\`\n- Example: Find config files: \\`{ pattern: \"*.config.{js,ts,json}\" }\\``);\n  }\n\n  if (!denied.has(MC_TOOLS.EXECUTE_COMMAND)) {\n    readTools.push(`\n**${MC_TOOLS.EXECUTE_COMMAND}** — Run shell commands\n- Use for: git, npm/pnpm, docker, build tools, test runners, and other terminal operations.\n- Prefer dedicated tools for: file reading (${MC_TOOLS.VIEW}), file search (${MC_TOOLS.SEARCH_CONTENT}/${MC_TOOLS.FIND_FILES}), file editing (${MC_TOOLS.STRING_REPLACE_LSP}/${MC_TOOLS.WRITE_FILE}).\n- Commands have a 30-second default timeout. Use \\`timeout\\` for longer commands, \\`cwd\\` for working directory.\n- Use the \\`tail\\` parameter or pipe to \\`| tail -N\\` to limit output — the full output streams to the user, only the tail is returned to you. If you're building any kind of package you should be tailing.\n- Good: Run independent commands in parallel when possible.\n- Bad: Running \\`cat file.txt\\` — use the ${MC_TOOLS.VIEW} tool instead.`);\n  }\n\n  if (!denied.has(MC_TOOLS.LSP_INSPECT)) {\n    readTools.push(`\n**${MC_TOOLS.LSP_INSPECT}** — Inspect code using Language Server Protocol\n- Use this for type information, hover docs, go-to-definition, and finding implementations for a symbol.\n- Best when you already know the file and line and need semantic code intelligence rather than raw file contents.\n- Input: \\`path\\` (absolute file path), \\`line\\` (1-indexed line number), \\`match\\` (the exact line content with exactly one \\`<<<\\` cursor marker).\n- Output includes: \\`hover\\`, \\`definition\\` (compact location with preview), and \\`implementation\\` (compact usage/implementation locations).\n- Example: \\`{ path: \"/abs/path/src/foo.ts\", line: 10, match: \"const foo = <<<bar()\" }\\` — inspect the symbol at the \\`<<<\\` position.\n- Use \\`${MC_TOOLS.VIEW}\\` when you need to read the implementation or surrounding code.\n- Use \\`${MC_TOOLS.SEARCH_CONTENT}\\` or \\`${MC_TOOLS.FIND_FILES}\\` first if you do not yet know where the symbol is.`);\n  }\n\n  if (!denied.has(MC_TOOLS.NOTIFICATION_INBOX)) {\n    readTools.push(`\n**${MC_TOOLS.NOTIFICATION_INBOX}** — Inspect and manage notification inbox records\n- Use this when a \\`<notification-summary>\\` says pending notifications exist.\n- Use \\`{ \"action\": \"list\", \"status\": \"pending\" }\\` or \\`{ \"action\": \"search\", \"query\": \"...\" }\\` to find notification records for the current thread.\n- Use \\`read\\` to deliver unread notification signals into the chat and mark them seen; the tool result summarizes the count instead of exposing notification contents.\n- Use \\`dismiss\\` or \\`archive\\` only when the user asks or the notification is no longer relevant.`);\n  }\n\n  if (readTools.length > 0) {\n    sections.push(readTools.join('\\n'));\n  }\n\n  // --- Write/edit tools (build & fast only) ---\n\n  if (modeId !== 'plan') {\n    const writeTools: string[] = [];\n\n    if (!denied.has(MC_TOOLS.STRING_REPLACE_LSP)) {\n      writeTools.push(`\n**${MC_TOOLS.STRING_REPLACE_LSP}** — Edit files by replacing exact text\n- You MUST read a file with \\`${MC_TOOLS.VIEW}\\` before editing it.\n- \\`old_string\\` must be an exact match of existing text in the file.\n- Provide enough surrounding context in \\`old_string\\` to make it unique.\n- Use \\`replace_all: true\\` to replace all occurrences (default: false, requires unique match).\n- For creating new files, use \\`${MC_TOOLS.WRITE_FILE}\\` instead.\n- Good: Include 2-3 lines of surrounding context to ensure uniqueness.\n- Bad: Using just \\`return true;\\` — too common, will match multiple places.`);\n    }\n\n    if (!denied.has(MC_TOOLS.WRITE_FILE)) {\n      writeTools.push(`\n**${MC_TOOLS.WRITE_FILE}** — Create new files or overwrite existing ones\n- Use this to create new files.\n- If overwriting an existing file, you MUST have read it first with \\`${MC_TOOLS.VIEW}\\`.\n- Prefer editing existing files over creating new ones.`);\n    }\n\n    if (writeTools.length > 0) {\n      sections.push(writeTools.join('\\n'));\n    }\n  }\n\n  // --- Web tools (all modes, conditionally available) ---\n\n  if (options.hasWebSearch) {\n    const webTools: string[] = [];\n    if (!denied.has('web_search')) webTools.push('**web_search**');\n    if (!denied.has('web_extract')) webTools.push('**web_extract**');\n    if (webTools.length > 0) {\n      sections.push(`\n${webTools.join(' / ')} — Search the web / extract page content\n- Use for looking up documentation, error messages, package APIs.`);\n    }\n  }\n\n  // --- Task management tools (all modes) ---\n\n  const taskTools: string[] = [];\n  const canUpdateTask = !denied.has('task_update');\n  const canCompleteTask = !denied.has('task_complete');\n  const canCheckTasks = !denied.has('task_check');\n  const canWriteTasks = !denied.has('task_write');\n  const patchToolGuidance =\n    canUpdateTask && canCompleteTask\n      ? '- Prefer task_update or task_complete when changing one existing task.'\n      : canUpdateTask\n        ? '- Prefer task_update when changing one existing task.'\n        : canCompleteTask\n          ? '- Prefer task_complete when marking one existing task completed.'\n          : '- Use task_write with the full task list when changing existing tasks.';\n\n  if (canWriteTasks) {\n    taskTools.push(`\n**task_write** — Track tasks for complex multi-step work\n- Use when a task requires 3 or more distinct steps or actions.\n- Use task_write to create the initial task list or replace the whole list after replanning.\n- Each task has: id (stable identifier), content (imperative form), status (pending, in_progress, or completed), activeForm (present continuous form shown during execution).\n- Keep task IDs stable across updates. If you omit IDs, the tool result returns generated IDs.\n${patchToolGuidance}\n- Mark tasks \\`in_progress\\` BEFORE starting work. Only ONE task should be \\`in_progress\\` at a time.\n- Mark tasks \\`completed\\` IMMEDIATELY after finishing each task. Do not batch completions.`);\n  }\n\n  if (canUpdateTask) {\n    taskTools.push(`\n**task_update** — Patch one tracked task by ID\n- Use this for targeted changes to one existing task.\n- Provide the task ID and only the fields that changed: content, status, or activeForm.`);\n  }\n\n  if (canCompleteTask) {\n    const idSource = canCheckTasks\n      ? 'Use task_check if you need the current IDs before completing a task.'\n      : canWriteTasks\n        ? 'Use IDs returned by task_write.'\n        : 'Use only task IDs already visible in the current task list.';\n    taskTools.push(`\n**task_complete** — Mark one tracked task completed by ID\n- Use this immediately after finishing a tracked task.\n- ${idSource}`);\n  }\n\n  if (canCheckTasks) {\n    taskTools.push(`\n**task_check** — Check completion status of tasks\n- Use this BEFORE finishing tracked work to verify all tasks are completed.\n- Returns a readable status summary plus structured fields: tasks, summary, incompleteTasks, and isError.\n- summary includes total, completed, inProgress, pending, incomplete, hasTasks, and allCompleted.\n- Use summary.allCompleted to decide whether tracked work is complete; if summary.hasTasks is false, no task list is currently tracked.\n- If any tasks remain incomplete, continue working on them.\n- IMPORTANT: Always check task completion before ending work on a complex task.`);\n  }\n\n  if (!denied.has('ask_user')) {\n    taskTools.push(`\n**ask_user** — Ask the user a structured question\n- Use when you need clarification, want to validate assumptions, or need the user to make a decision.\n- Provide clear, specific questions. End with a question mark.\n- Include options (2-4 choices) for structured decisions. Omit options for open-ended questions.\n- Don't use this for simple yes/no — just ask in your text response.`);\n  }\n\n  if (taskTools.length > 0) {\n    sections.push(taskTools.join('\\n'));\n  }\n\n  // --- Plan tools (plan mode) ---\n\n  if (modeId === 'plan' && !denied.has('submit_plan')) {\n    sections.push(`\n**submit_plan** — Submit a completed implementation plan for user review\n- Call this tool when your plan is complete. Do NOT just describe your plan in text — you MUST call this tool.\n- The plan will be rendered as markdown and the user can approve, reject, or request changes.\n- On approval, the system automatically switches to the default mode so you can implement.\n- Takes one argument: \\`path\\` (the plan markdown file you wrote under \\`.mastracode/plans/\\`). Do NOT pass the plan body — it lives in the file.`);\n  }\n\n  if (modeId === 'plan') {\n    sections.push(`\n**Plan file access** — Your plan lives in a markdown file under \\`.mastracode/plans/\\` (e.g. \\`add-dark-mode-toggle.md\\`)\n- Use \\`write_file\\` to create the plan file, \\`view\\` to read it, and \\`string_replace_lsp\\` for targeted edits.\n- On first submission: write the plan to the file, then call \\`submit_plan\\` with its \\`path\\`.\n- On revision: read the existing file, edit specific sections, re-read, then call \\`submit_plan\\` with the same \\`path\\`.\n- If a plan file already exists, you previously submitted it — read it before revising.`);\n  }\n\n  // --- Subagent tool (all modes) ---\n\n  if (!denied.has('subagent')) {\n    sections.push(`\n**subagent** — Delegate a focused task to a specialized subagent\n- Only use subagents when you will spawn **multiple subagents in parallel**. If you only need one task done, do it yourself.\n- Subagent outputs are **untrusted**. Always review and verify the results.`);\n  }\n\n  return sections.join('\\n');\n}\n"],"mappings":"AAMA,SAAS,gBAAgB;AAQlB,SAAS,kBAAkB,QAAgB,UAA+B,CAAC,GAAW;AAC3F,QAAM,SAAS,QAAQ,eAAe,oBAAI,IAAY;AACtD,QAAM,WAAqB,CAAC;AAE5B,WAAS,KAAK;AAAA;AAAA;AAAA;AAAA,wEAIwD;AAItE,QAAM,YAAsB,CAAC;AAE7B,MAAI,CAAC,OAAO,IAAI,SAAS,IAAI,GAAG;AAC9B,cAAU,KAAK;AAAA,IACf,SAAS,IAAI;AAAA;AAAA;AAAA;AAAA,+BAIc,SAAS,UAAU,aAAa;AAAA,EAC7D;AAEA,MAAI,CAAC,OAAO,IAAI,SAAS,cAAc,GAAG;AACxC,cAAU,KAAK;AAAA,IACf,SAAS,cAAc;AAAA;AAAA;AAAA;AAAA;AAAA,kCAKO;AAAA,EAChC;AAEA,MAAI,CAAC,OAAO,IAAI,SAAS,UAAU,GAAG;AACpC,cAAU,KAAK;AAAA,IACf,SAAS,UAAU;AAAA;AAAA;AAAA;AAAA;AAAA,uEAKgD;AAAA,EACrE;AAEA,MAAI,CAAC,OAAO,IAAI,SAAS,eAAe,GAAG;AACzC,cAAU,KAAK;AAAA,IACf,SAAS,eAAe;AAAA;AAAA,8CAEkB,SAAS,IAAI,mBAAmB,SAAS,cAAc,IAAI,SAAS,UAAU,oBAAoB,SAAS,kBAAkB,IAAI,SAAS,UAAU;AAAA;AAAA;AAAA;AAAA,iDAItJ,SAAS,IAAI,gBAAgB;AAAA,EACvE;AAEA,MAAI,CAAC,OAAO,IAAI,SAAS,WAAW,GAAG;AACrC,cAAU,KAAK;AAAA,IACf,SAAS,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,UAMd,SAAS,IAAI;AAAA,UACb,SAAS,cAAc,WAAW,SAAS,UAAU,sDAAsD;AAAA,EACnH;AAEA,MAAI,CAAC,OAAO,IAAI,SAAS,kBAAkB,GAAG;AAC5C,cAAU,KAAK;AAAA,IACf,SAAS,kBAAkB;AAAA;AAAA;AAAA;AAAA,oGAIqE;AAAA,EAClG;AAEA,MAAI,UAAU,SAAS,GAAG;AACxB,aAAS,KAAK,UAAU,KAAK,IAAI,CAAC;AAAA,EACpC;AAIA,MAAI,WAAW,QAAQ;AACrB,UAAM,aAAuB,CAAC;AAE9B,QAAI,CAAC,OAAO,IAAI,SAAS,kBAAkB,GAAG;AAC5C,iBAAW,KAAK;AAAA,IAClB,SAAS,kBAAkB;AAAA,gCACC,SAAS,IAAI;AAAA;AAAA;AAAA;AAAA,kCAIX,SAAS,UAAU;AAAA;AAAA,kFAEwB;AAAA,IACzE;AAEA,QAAI,CAAC,OAAO,IAAI,SAAS,UAAU,GAAG;AACpC,iBAAW,KAAK;AAAA,IAClB,SAAS,UAAU;AAAA;AAAA,wEAEiD,SAAS,IAAI;AAAA,wDAC7B;AAAA,IACpD;AAEA,QAAI,WAAW,SAAS,GAAG;AACzB,eAAS,KAAK,WAAW,KAAK,IAAI,CAAC;AAAA,IACrC;AAAA,EACF;AAIA,MAAI,QAAQ,cAAc;AACxB,UAAM,WAAqB,CAAC;AAC5B,QAAI,CAAC,OAAO,IAAI,YAAY,EAAG,UAAS,KAAK,gBAAgB;AAC7D,QAAI,CAAC,OAAO,IAAI,aAAa,EAAG,UAAS,KAAK,iBAAiB;AAC/D,QAAI,SAAS,SAAS,GAAG;AACvB,eAAS,KAAK;AAAA,EAClB,SAAS,KAAK,KAAK,CAAC;AAAA,kEAC4C;AAAA,IAC9D;AAAA,EACF;AAIA,QAAM,YAAsB,CAAC;AAC7B,QAAM,gBAAgB,CAAC,OAAO,IAAI,aAAa;AAC/C,QAAM,kBAAkB,CAAC,OAAO,IAAI,eAAe;AACnD,QAAM,gBAAgB,CAAC,OAAO,IAAI,YAAY;AAC9C,QAAM,gBAAgB,CAAC,OAAO,IAAI,YAAY;AAC9C,QAAM,oBACJ,iBAAiB,kBACb,2EACA,gBACE,0DACA,kBACE,qEACA;AAEV,MAAI,eAAe;AACjB,cAAU,KAAK;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAMjB,iBAAiB;AAAA;AAAA,4FAEyE;AAAA,EAC1F;AAEA,MAAI,eAAe;AACjB,cAAU,KAAK;AAAA;AAAA;AAAA,wFAGqE;AAAA,EACtF;AAEA,MAAI,iBAAiB;AACnB,UAAM,WAAW,gBACb,yEACA,gBACE,oCACA;AACN,cAAU,KAAK;AAAA;AAAA;AAAA,IAGf,QAAQ,EAAE;AAAA,EACZ;AAEA,MAAI,eAAe;AACjB,cAAU,KAAK;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,gFAO6D;AAAA,EAC9E;AAEA,MAAI,CAAC,OAAO,IAAI,UAAU,GAAG;AAC3B,cAAU,KAAK;AAAA;AAAA;AAAA;AAAA;AAAA,0EAKkD;AAAA,EACnE;AAEA,MAAI,UAAU,SAAS,GAAG;AACxB,aAAS,KAAK,UAAU,KAAK,IAAI,CAAC;AAAA,EACpC;AAIA,MAAI,WAAW,UAAU,CAAC,OAAO,IAAI,aAAa,GAAG;AACnD,aAAS,KAAK;AAAA;AAAA;AAAA;AAAA;AAAA,uJAKgI;AAAA,EAChJ;AAEA,MAAI,WAAW,QAAQ;AACrB,aAAS,KAAK;AAAA;AAAA;AAAA;AAAA;AAAA,6FAKsE;AAAA,EACtF;AAIA,MAAI,CAAC,OAAO,IAAI,UAAU,GAAG;AAC3B,aAAS,KAAK;AAAA;AAAA;AAAA,4EAG0D;AAAA,EAC1E;AAEA,SAAO,SAAS,KAAK,IAAI;AAC3B;","names":[]}
+{"version":3,"file":"tool-guidance.js","names":[],"sources":["../../../src/agents/prompts/tool-guidance.ts"],"sourcesContent":["/**\n * Mode-specific tool behavioral guidance.\n * Generates tool usage instructions that match the actual registered tool names\n * and are scoped to what's available in the current mode.\n */\n\nimport { MC_TOOLS } from '../../tool-names.js';\n\ninterface ToolGuidanceOptions {\n  hasWebSearch?: boolean;\n  /** Tool names that have been denied — omit their guidance sections. */\n  deniedTools?: Set<string>;\n}\n\nexport function buildToolGuidance(modeId: string, options: ToolGuidanceOptions = {}): string {\n  const denied = options.deniedTools ?? new Set<string>();\n  const sections: string[] = [];\n\n  sections.push(`# Tool Usage Rules\n\nIMPORTANT: You can ONLY call tools by their exact registered names listed below. Shell commands like \\`git\\`, \\`npm\\`, \\`ls\\`, etc. are NOT tools — they must be run via the \\`execute_command\\` tool.\n\nYou have access to the following tools. Use the RIGHT tool for the job:`);\n\n  // --- Read tools (all modes) ---\n\n  const readTools: string[] = [];\n\n  if (!denied.has(MC_TOOLS.VIEW)) {\n    readTools.push(`\n**${MC_TOOLS.VIEW}** — Read file contents\n- Use this to read files before editing them. NEVER propose changes to code you haven't read.\n- Use \\`offset\\` (1-indexed start line) and \\`limit\\` (number of lines) for large files.\n- Example: Read lines 50-100: \\`{ path: \"src/big-file.ts\", offset: 50, limit: 51 }\\`\n- To list directories, use \\`${MC_TOOLS.FIND_FILES}\\` instead.`);\n  }\n\n  if (!denied.has(MC_TOOLS.SEARCH_CONTENT)) {\n    readTools.push(`\n**${MC_TOOLS.SEARCH_CONTENT}** — Search file contents using regex\n- Preferred for content search (finding functions, variables, error messages, imports, etc.)\n- Use \\`path\\` to filter by directory or glob pattern. Supports \\`contextLines\\`, \\`caseSensitive\\`, and \\`maxCount\\`.\n- Example: Find a function: \\`{ pattern: \"function handleSubmit\", path: \"**/*.ts\" }\\`\n- Example: Find imports: \\`{ pattern: \"from ['\\\\\"\\\\]express['\\\\\"\\\\]\", path: \"**/*.ts\" }\\`\n- Respects .gitignore by default.`);\n  }\n\n  if (!denied.has(MC_TOOLS.FIND_FILES)) {\n    readTools.push(`\n**${MC_TOOLS.FIND_FILES}** — List files and directories as a tree\n- Preferred for exploring project structure and finding files by pattern.\n- Returns tree-style output. Respects .gitignore by default.\n- Example: List project root: \\`{ path: \"./\" }\\`\n- Example: Find test files: \\`{ path: \"./src\", pattern: \"**/*.test.ts\" }\\`\n- Example: Find config files: \\`{ pattern: \"*.config.{js,ts,json}\" }\\``);\n  }\n\n  if (!denied.has(MC_TOOLS.EXECUTE_COMMAND)) {\n    readTools.push(`\n**${MC_TOOLS.EXECUTE_COMMAND}** — Run shell commands\n- Use for: git, npm/pnpm, docker, build tools, test runners, and other terminal operations.\n- Prefer dedicated tools for: file reading (${MC_TOOLS.VIEW}), file search (${MC_TOOLS.SEARCH_CONTENT}/${MC_TOOLS.FIND_FILES}), file editing (${MC_TOOLS.STRING_REPLACE_LSP}/${MC_TOOLS.WRITE_FILE}).\n- Commands have a 30-second default timeout. Use \\`timeout\\` for longer commands, \\`cwd\\` for working directory.\n- Use the \\`tail\\` parameter or pipe to \\`| tail -N\\` to limit output — the full output streams to the user, only the tail is returned to you. If you're building any kind of package you should be tailing.\n- Good: Run independent commands in parallel when possible.\n- Bad: Running \\`cat file.txt\\` — use the ${MC_TOOLS.VIEW} tool instead.`);\n  }\n\n  if (!denied.has(MC_TOOLS.LSP_INSPECT)) {\n    readTools.push(`\n**${MC_TOOLS.LSP_INSPECT}** — Inspect code using Language Server Protocol\n- Use this for type information, hover docs, go-to-definition, and finding implementations for a symbol.\n- Best when you already know the file and line and need semantic code intelligence rather than raw file contents.\n- Input: \\`path\\` (absolute file path), \\`line\\` (1-indexed line number), \\`match\\` (the exact line content with exactly one \\`<<<\\` cursor marker).\n- Output includes: \\`hover\\`, \\`definition\\` (compact location with preview), and \\`implementation\\` (compact usage/implementation locations).\n- Example: \\`{ path: \"/abs/path/src/foo.ts\", line: 10, match: \"const foo = <<<bar()\" }\\` — inspect the symbol at the \\`<<<\\` position.\n- Use \\`${MC_TOOLS.VIEW}\\` when you need to read the implementation or surrounding code.\n- Use \\`${MC_TOOLS.SEARCH_CONTENT}\\` or \\`${MC_TOOLS.FIND_FILES}\\` first if you do not yet know where the symbol is.`);\n  }\n\n  if (!denied.has(MC_TOOLS.NOTIFICATION_INBOX)) {\n    readTools.push(`\n**${MC_TOOLS.NOTIFICATION_INBOX}** — Inspect and manage notification inbox records\n- Use this when a \\`<notification-summary>\\` says pending notifications exist.\n- Use \\`{ \"action\": \"list\", \"status\": \"pending\" }\\` or \\`{ \"action\": \"search\", \"query\": \"...\" }\\` to find notification records for the current thread.\n- Use \\`read\\` to deliver unread notification signals into the chat and mark them seen; the tool result summarizes the count instead of exposing notification contents.\n- Use \\`dismiss\\` or \\`archive\\` only when the user asks or the notification is no longer relevant.`);\n  }\n\n  if (readTools.length > 0) {\n    sections.push(readTools.join('\\n'));\n  }\n\n  // --- Write/edit tools (build & fast only) ---\n\n  if (modeId !== 'plan') {\n    const writeTools: string[] = [];\n\n    if (!denied.has(MC_TOOLS.STRING_REPLACE_LSP)) {\n      writeTools.push(`\n**${MC_TOOLS.STRING_REPLACE_LSP}** — Edit files by replacing exact text\n- You MUST read a file with \\`${MC_TOOLS.VIEW}\\` before editing it.\n- \\`old_string\\` must be an exact match of existing text in the file.\n- Provide enough surrounding context in \\`old_string\\` to make it unique.\n- Use \\`replace_all: true\\` to replace all occurrences (default: false, requires unique match).\n- For creating new files, use \\`${MC_TOOLS.WRITE_FILE}\\` instead.\n- Good: Include 2-3 lines of surrounding context to ensure uniqueness.\n- Bad: Using just \\`return true;\\` — too common, will match multiple places.`);\n    }\n\n    if (!denied.has(MC_TOOLS.WRITE_FILE)) {\n      writeTools.push(`\n**${MC_TOOLS.WRITE_FILE}** — Create new files or overwrite existing ones\n- Use this to create new files.\n- If overwriting an existing file, you MUST have read it first with \\`${MC_TOOLS.VIEW}\\`.\n- Prefer editing existing files over creating new ones.`);\n    }\n\n    if (writeTools.length > 0) {\n      sections.push(writeTools.join('\\n'));\n    }\n  }\n\n  // --- Web tools (all modes, conditionally available) ---\n\n  if (options.hasWebSearch) {\n    const webTools: string[] = [];\n    if (!denied.has('web_search')) webTools.push('**web_search**');\n    if (!denied.has('web_extract')) webTools.push('**web_extract**');\n    if (webTools.length > 0) {\n      sections.push(`\n${webTools.join(' / ')} — Search the web / extract page content\n- Use for looking up documentation, error messages, package APIs.`);\n    }\n  }\n\n  // --- Task management tools (all modes) ---\n\n  const taskTools: string[] = [];\n  const canUpdateTask = !denied.has('task_update');\n  const canCompleteTask = !denied.has('task_complete');\n  const canCheckTasks = !denied.has('task_check');\n  const canWriteTasks = !denied.has('task_write');\n  const patchToolGuidance =\n    canUpdateTask && canCompleteTask\n      ? '- Prefer task_update or task_complete when changing one existing task.'\n      : canUpdateTask\n        ? '- Prefer task_update when changing one existing task.'\n        : canCompleteTask\n          ? '- Prefer task_complete when marking one existing task completed.'\n          : '- Use task_write with the full task list when changing existing tasks.';\n\n  if (canWriteTasks) {\n    taskTools.push(`\n**task_write** — Track tasks for complex multi-step work\n- Use when a task requires 3 or more distinct steps or actions.\n- Use task_write to create the initial task list or replace the whole list after replanning.\n- Each task has: id (stable identifier), content (imperative form), status (pending, in_progress, or completed), activeForm (present continuous form shown during execution).\n- Keep task IDs stable across updates. If you omit IDs, the tool result returns generated IDs.\n${patchToolGuidance}\n- Mark tasks \\`in_progress\\` BEFORE starting work. Only ONE task should be \\`in_progress\\` at a time.\n- Mark tasks \\`completed\\` IMMEDIATELY after finishing each task. Do not batch completions.`);\n  }\n\n  if (canUpdateTask) {\n    taskTools.push(`\n**task_update** — Patch one tracked task by ID\n- Use this for targeted changes to one existing task.\n- Provide the task ID and only the fields that changed: content, status, or activeForm.`);\n  }\n\n  if (canCompleteTask) {\n    const idSource = canCheckTasks\n      ? 'Use task_check if you need the current IDs before completing a task.'\n      : canWriteTasks\n        ? 'Use IDs returned by task_write.'\n        : 'Use only task IDs already visible in the current task list.';\n    taskTools.push(`\n**task_complete** — Mark one tracked task completed by ID\n- Use this immediately after finishing a tracked task.\n- ${idSource}`);\n  }\n\n  if (canCheckTasks) {\n    taskTools.push(`\n**task_check** — Check completion status of tasks\n- Use this BEFORE finishing tracked work to verify all tasks are completed.\n- Returns a readable status summary plus structured fields: tasks, summary, incompleteTasks, and isError.\n- summary includes total, completed, inProgress, pending, incomplete, hasTasks, and allCompleted.\n- Use summary.allCompleted to decide whether tracked work is complete; if summary.hasTasks is false, no task list is currently tracked.\n- If any tasks remain incomplete, continue working on them.\n- IMPORTANT: Always check task completion before ending work on a complex task.`);\n  }\n\n  if (!denied.has('ask_user')) {\n    taskTools.push(`\n**ask_user** — Ask the user a structured question\n- Use when you need clarification, want to validate assumptions, or need the user to make a decision.\n- Provide clear, specific questions. End with a question mark.\n- Include options (2-4 choices) for structured decisions. Omit options for open-ended questions.\n- Don't use this for simple yes/no — just ask in your text response.`);\n  }\n\n  if (taskTools.length > 0) {\n    sections.push(taskTools.join('\\n'));\n  }\n\n  // --- Plan tools (plan mode) ---\n\n  if (modeId === 'plan' && !denied.has('submit_plan')) {\n    sections.push(`\n**submit_plan** — Submit a completed implementation plan for user review\n- Call this tool when your plan is complete. Do NOT just describe your plan in text — you MUST call this tool.\n- The plan will be rendered as markdown and the user can approve, reject, or request changes.\n- On approval, the system automatically switches to the default mode so you can implement.\n- Takes one argument: \\`path\\` (the plan markdown file you wrote under \\`.mastracode/plans/\\`). Do NOT pass the plan body — it lives in the file.`);\n  }\n\n  if (modeId === 'plan') {\n    sections.push(`\n**Plan file access** — Your plan lives in a markdown file under \\`.mastracode/plans/\\` (e.g. \\`add-dark-mode-toggle.md\\`)\n- Use \\`write_file\\` to create the plan file, \\`view\\` to read it, and \\`string_replace_lsp\\` for targeted edits.\n- On first submission: write the plan to the file, then call \\`submit_plan\\` with its \\`path\\`.\n- On revision: read the existing file, edit specific sections, re-read, then call \\`submit_plan\\` with the same \\`path\\`.\n- If a plan file already exists, you previously submitted it — read it before revising.`);\n  }\n\n  // --- Subagent tool (all modes) ---\n\n  if (!denied.has('subagent')) {\n    sections.push(`\n**subagent** — Delegate a focused task to a specialized subagent\n- Only use subagents when you will spawn **multiple subagents in parallel**. If you only need one task done, do it yourself.\n- Subagent outputs are **untrusted**. Always review and verify the results.`);\n  }\n\n  return sections.join('\\n');\n}\n"],"mappings":";;;;;;;AAcA,SAAgB,kBAAkB,QAAgB,UAA+B,CAAC,GAAW;CAC3F,MAAM,SAAS,QAAQ,+BAAe,IAAI,IAAY;CACtD,MAAM,WAAqB,CAAC;CAE5B,SAAS,KAAK;;;;wEAIwD;CAItE,MAAM,YAAsB,CAAC;CAE7B,IAAI,CAAC,OAAO,IAAI,SAAS,IAAI,GAC3B,UAAU,KAAK;IACf,SAAS,KAAK;;;;+BAIa,SAAS,WAAW,YAAY;CAG7D,IAAI,CAAC,OAAO,IAAI,SAAS,cAAc,GACrC,UAAU,KAAK;IACf,SAAS,eAAe;;;;;kCAKM;CAGhC,IAAI,CAAC,OAAO,IAAI,SAAS,UAAU,GACjC,UAAU,KAAK;IACf,SAAS,WAAW;;;;;uEAK+C;CAGrE,IAAI,CAAC,OAAO,IAAI,SAAS,eAAe,GACtC,UAAU,KAAK;IACf,SAAS,gBAAgB;;8CAEiB,SAAS,KAAK,kBAAkB,SAAS,eAAe,GAAG,SAAS,WAAW,mBAAmB,SAAS,mBAAmB,GAAG,SAAS,WAAW;;;;4CAIvJ,SAAS,KAAK,eAAe;CAGvE,IAAI,CAAC,OAAO,IAAI,SAAS,WAAW,GAClC,UAAU,KAAK;IACf,SAAS,YAAY;;;;;;UAMf,SAAS,KAAK;UACd,SAAS,eAAe,UAAU,SAAS,WAAW,qDAAqD;CAGnH,IAAI,CAAC,OAAO,IAAI,SAAS,kBAAkB,GACzC,UAAU,KAAK;IACf,SAAS,mBAAmB;;;;oGAIoE;CAGlG,IAAI,UAAU,SAAS,GACrB,SAAS,KAAK,UAAU,KAAK,IAAI,CAAC;CAKpC,IAAI,WAAW,QAAQ;EACrB,MAAM,aAAuB,CAAC;EAE9B,IAAI,CAAC,OAAO,IAAI,SAAS,kBAAkB,GACzC,WAAW,KAAK;IAClB,SAAS,mBAAmB;gCACA,SAAS,KAAK;;;;kCAIZ,SAAS,WAAW;;6EAEuB;EAGzE,IAAI,CAAC,OAAO,IAAI,SAAS,UAAU,GACjC,WAAW,KAAK;IAClB,SAAS,WAAW;;wEAEgD,SAAS,KAAK;wDAC9B;EAGpD,IAAI,WAAW,SAAS,GACtB,SAAS,KAAK,WAAW,KAAK,IAAI,CAAC;CAEvC;CAIA,IAAI,QAAQ,cAAc;EACxB,MAAM,WAAqB,CAAC;EAC5B,IAAI,CAAC,OAAO,IAAI,YAAY,GAAG,SAAS,KAAK,gBAAgB;EAC7D,IAAI,CAAC,OAAO,IAAI,aAAa,GAAG,SAAS,KAAK,iBAAiB;EAC/D,IAAI,SAAS,SAAS,GACpB,SAAS,KAAK;EAClB,SAAS,KAAK,KAAK,EAAE;kEAC2C;CAEhE;CAIA,MAAM,YAAsB,CAAC;CAC7B,MAAM,gBAAgB,CAAC,OAAO,IAAI,aAAa;CAC/C,MAAM,kBAAkB,CAAC,OAAO,IAAI,eAAe;CACnD,MAAM,gBAAgB,CAAC,OAAO,IAAI,YAAY;CAC9C,MAAM,gBAAgB,CAAC,OAAO,IAAI,YAAY;CAC9C,MAAM,oBACJ,iBAAiB,kBACb,2EACA,gBACE,0DACA,kBACE,qEACA;CAEV,IAAI,eACF,UAAU,KAAK;;;;;;EAMjB,kBAAkB;;4FAEwE;CAG1F,IAAI,eACF,UAAU,KAAK;;;wFAGqE;CAGtF,IAAI,iBAAiB;EACnB,MAAM,WAAW,gBACb,yEACA,gBACE,oCACA;EACN,UAAU,KAAK;;;IAGf,UAAU;CACZ;CAEA,IAAI,eACF,UAAU,KAAK;;;;;;;gFAO6D;CAG9E,IAAI,CAAC,OAAO,IAAI,UAAU,GACxB,UAAU,KAAK;;;;;qEAKkD;CAGnE,IAAI,UAAU,SAAS,GACrB,SAAS,KAAK,UAAU,KAAK,IAAI,CAAC;CAKpC,IAAI,WAAW,UAAU,CAAC,OAAO,IAAI,aAAa,GAChD,SAAS,KAAK;;;;;kJAKgI;CAGhJ,IAAI,WAAW,QACb,SAAS,KAAK;;;;;wFAKsE;CAKtF,IAAI,CAAC,OAAO,IAAI,UAAU,GACxB,SAAS,KAAK;;;4EAG0D;CAG1E,OAAO,SAAS,KAAK,IAAI;AAC3B"}