pybao-cli 1.5.5 → 1.5.7

package/dist/{chunk-SIERUHXD.js → chunk-SWNNPHFY.js}

@@ -2,11 +2,11 @@ import { createRequire as __pybCreateRequire } from "node:module";
 const require = __pybCreateRequire(import.meta.url);
 import {
   listPybAgentSessions
-} from "./chunk-DXRP66I5.js";
+} from "./chunk-JEAXJP2E.js";
 import {
   formatValidationResult,
   validatePluginOrMarketplacePath
-} from "./chunk-K6JHXMXN.js";
+} from "./chunk-5JKCAVMI.js";
 import {
   ConversationTracker,
   appendFinishState,
@@ -14,18 +14,18 @@ import {
   getConversationTrackerForContext,
   isFinishComplete,
   mapFinishReason
-} from "./chunk-5XJMA67J.js";
+} from "./chunk-CJ2YYIJN.js";
 import {
   beginReplSessionScope
 } from "./chunk-F4AXICO7.js";
 import {
   loadPybAgentSessionMessages
-} from "./chunk-HOPQEHPL.js";
+} from "./chunk-4R7NUADF.js";
 import {
   appendSessionCustomTitleRecord,
   appendSessionJsonlFromMessage,
   appendSessionTagRecord
-} from "./chunk-LIWSSSFH.js";
+} from "./chunk-ZD6NMP33.js";
 import {
   drainHookSystemPromptAdditions,
   getHookTranscriptPath,
@@ -37,7 +37,7 @@ import {
   runStopHooks,
   runUserPromptSubmitHooks,
   updateHookTranscriptForMessages
-} from "./chunk-LJ5LSGNH.js";
+} from "./chunk-T7UTA73F.js";
 import {
   DEFAULT_OUTPUT_STYLE,
   getAvailableOutputStyles,
@@ -46,11 +46,11 @@ import {
   getOutputStyleSystemPromptAdditions,
   resolveOutputStyleName,
   setCurrentOutputStyle
-} from "./chunk-K7WUKXHI.js";
+} from "./chunk-3JH34RBY.js";
 import {
   fetchCustomModels,
   getModelFeatures
-} from "./chunk-WZMYF3UX.js";
+} from "./chunk-4BFEUSKN.js";
 import {
   getSessionState
 } from "./chunk-XKYHFZEC.js";
@@ -58,7 +58,7 @@ import {
   queryLLM,
   queryQuick,
   verifyApiKey
-} from "./chunk-SSJEKON3.js";
+} from "./chunk-KLD4WAB6.js";
 import {
   DEFAULT_TIMEOUT_MS,
   FallbackToolUseRejectedMessage,
@@ -72,7 +72,7 @@ import {
   listMCPServers,
   loadMergedSettings,
   normalizeSandboxRuntimeConfigFromSettings
-} from "./chunk-HE7KJ6UH.js";
+} from "./chunk-OY6SB5B3.js";
 import {
   addMarketplace,
   disableSkillPlugin,
@@ -85,11 +85,11 @@ import {
   refreshMarketplaceAsync,
   removeMarketplace,
   uninstallSkillPlugin
-} from "./chunk-6LPSL7BE.js";
+} from "./chunk-VBV5RHIK.js";
 import {
   loadToolPermissionContextFromDisk,
   persistToolPermissionUpdateToDisk
-} from "./chunk-ZRKIN5IB.js";
+} from "./chunk-7FFBXWS3.js";
 import {
   applyToolPermissionContextUpdate,
   applyToolPermissionContextUpdates,
@@ -100,13 +100,13 @@ import {
   generateSystemReminders,
   resetReminderSession,
   systemReminderService
-} from "./chunk-5SIMKDX4.js";
+} from "./chunk-IOP3VA4X.js";
 import {
   clearAgentCache,
   getActiveAgents,
   getAgentByType,
   getAllAgents
-} from "./chunk-TEC2E3XN.js";
+} from "./chunk-PI5RBPFA.js";
 import {
   API_ERROR_MESSAGE_PREFIX,
   CANCEL_MESSAGE,
@@ -137,7 +137,7 @@ import {
   processUserInput,
   reorderMessages,
   stripSystemMessages
-} from "./chunk-RAGFOLYJ.js";
+} from "./chunk-YNGGZILT.js";
 import {
   getRequestStatus,
   setRequestStatus,
@@ -167,7 +167,7 @@ import {
   normalizeFilePath,
   readTextContent,
   writeTextContent
-} from "./chunk-334FYYPK.js";
+} from "./chunk-SDKYJZWD.js";
 import {
   parseBlockEdits
 } from "./chunk-QWIBSCDN.js";
@@ -177,18 +177,18 @@ import {
   ParserRegistry,
   initParser,
   loadLanguage
-} from "./chunk-XYTFEOBP.js";
+} from "./chunk-EGJRWKZ6.js";
 import {
   getSettingsFileCandidates,
   loadSettingsWithLegacyFallback,
   readSettingsFile
-} from "./chunk-K6NWBOPY.js";
+} from "./chunk-5F6IQJHF.js";
 import {
   getCustomCommandDirectories,
   hasCustomCommands,
   loadCustomCommands,
   reloadCustomCommands
-} from "./chunk-YPKIYICA.js";
+} from "./chunk-VZDDKAL2.js";
 import {
   getSessionPlugins
 } from "./chunk-BJSWTHRM.js";
@@ -197,7 +197,7 @@ import {
   buildModelProfileKey,
   getModelManager,
   isDefaultSlowAndCapableModel
-} from "./chunk-CHIAWBUA.js";
+} from "./chunk-LYMH46VN.js";
 import {
   getCodeStyle,
   getContext,
@@ -205,16 +205,16 @@ import {
   getIsGit,
   getProjectDocs,
   getProjectStructureStatisticsBlock
-} from "./chunk-3EXYSVHB.js";
+} from "./chunk-IFC2PLAM.js";
 import {
   getRipgrepPath,
   getRipgrepPolicyMode,
   resolveRipgrepPolicy,
   ripGrep
-} from "./chunk-NVE4LCWO.js";
+} from "./chunk-EN7L7JWN.js";
 import {
   getTheme
-} from "./chunk-5UMUKAAM.js";
+} from "./chunk-Y2RSIF7P.js";
 import {
   DEFAULT_GLOBAL_CONFIG,
   enableConfigs,
@@ -227,7 +227,7 @@ import {
   saveGlobalConfig,
   setAllPointersToModel,
   setModelPointer
-} from "./chunk-WABSMUT4.js";
+} from "./chunk-PMYMUSB4.js";
 import {
   AbortError
 } from "./chunk-RQVLBMP7.js";
@@ -236,7 +236,7 @@ import {
   getCurrentRequest,
   logUserFriendly,
   markPhase
-} from "./chunk-UOMNQX6X.js";
+} from "./chunk-IKMMFSNJ.js";
 import {
   ASCII_LOGO,
   BunShell,
@@ -277,10 +277,10 @@ import {
   setCwd,
   shouldApplyToolOutputTruncation,
   truncateToolOutput
-} from "./chunk-RGKCFZJC.js";
+} from "./chunk-TIMEEE5U.js";
 import {
   MACRO
-} from "./chunk-OD44XENK.js";
+} from "./chunk-W4PXRGP3.js";
 import {
   __export
 } from "./chunk-I3J4JYES.js";
@@ -461,7 +461,7 @@ var getCommandSubcommandPrefix = memoize(
 var getCommandPrefix = memoize(
   async (command4, abortSignal) => {
     const { systemPrompt, userPrompt } = buildBashCommandPrefixDetectionPrompt(command4);
-    const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryQuick: queryQuick2 } = await import("./llm-Q23IAP4O.js");
+    const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryQuick: queryQuick2 } = await import("./llm-T7C6QJWB.js");
     const response = await queryQuick2({
       systemPrompt,
       userPrompt,
@@ -4263,7 +4263,7 @@ function formatParseError(error) {
   return error instanceof Error ? error.message : String(error);
 }
 async function defaultGateQuery(args) {
-  const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryLLM: queryLLM2 } = await import("./llm-Q23IAP4O.js");
+  const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryLLM: queryLLM2 } = await import("./llm-T7C6QJWB.js");
   const queryLLMFn = args.queryLLMOverride ?? queryLLM2;
   const messages = [
     {
@@ -6624,7 +6624,7 @@ var FileEditTool = {
     const originalFileContent = currentFileContent;
     let totalPatch = [];
     const { SmartEdit } = await import("./smart-edit-AWHJDSU6.js");
-    const { findLspAnchor } = await import("./lspAnchor-UJC5DJXX.js");
+    const { findLspAnchor } = await import("./lspAnchor-IZ7YQJ64.js");
     for (const op of editOperations) {
       const normalizedSearch = normalizeLineEndings(op.search);
       const normalizedReplace = normalizeLineEndings(op.replace);
@@ -8107,7 +8107,7 @@ import { z as z6 } from "zod";
 
 // src/tools/filesystem/GlobTool/prompt.ts
 var TOOL_NAME_FOR_PROMPT2 = "Glob";
-var DESCRIPTION4 = `- Fast file pattern matching tool that works with any codebase size
+var DESCRIPTION4 = `Fast file pattern matching tool that works with any codebase size
 
   ## WhenToUse & Best Practice
   - If you have keywords or fuzzy paths, use Glob first to narrow candidates.
@@ -8134,11 +8134,70 @@ var DESCRIPTION4 = `- Fast file pattern matching tool that works with any codeba
 
   ## Usage Details
   - Supports glob patterns like "**/*.js" or "src/**/*.ts"
-  - Returns matching file paths sorted by modification time
+  - Returns absolute file paths sorted by modification time (most recent first)
   - Use this tool when you need to find files by name patterns
-  - **Semantic Search**: Set \`semantic: true\` to use LSP workspace symbols when file-name matching fails. The \`pattern\` is treated as the symbol name.
-  - Semantic search is explicit: enable it only when normal matching fails or semantic lookup is required.
-  - If LSP is unavailable, it falls back to standard glob results without impacting the main file-finding flow.`;
+  - Powered by ripgrep with \`--files\` mode for fast pattern matching
+  - \`path\` parameter: Specify the directory to search in. If omitted, uses the current working directory. IMPORTANT: Omit this field to use the default directory. DO NOT enter "undefined" or "null" - simply omit it for the default behavior. Supports both relative and absolute paths.
+  - Results are limited to 100 files by default. If truncated, use a more specific path or pattern to narrow results.
+  - Search ignores .gitignore rules and includes hidden files by default.
+  - **Semantic Search**: Set \`semantic: true\` to enable LSP workspace symbol search as fallback.
+    - Trigger condition: Semantic search only activates when normal glob returns zero results.
+    - In semantic mode, the \`pattern\` parameter is interpreted as a symbol name (e.g., class name, function name) for LSP workspace symbol lookup.
+    - Returns file paths where the symbol is defined, helping locate source files by symbol name rather than filename pattern.
+    - On success: returns notice "Semantic search: added X results. Next: use LspTool for details."
+    - If LSP is unavailable, returns empty results with notice "Semantic search: LSP unavailable."
+  - **Empty Results**: When no files are found, use LS to confirm directory structure, then try broader patterns (e.g., src/**/*) or enable semantic search.
+  - **Error Handling**: Returns error if \`path\` does not exist or is not a valid directory.
+
+  ## Typical Usage Examples
+
+  ### Example 1: Project Structure Discovery (Unknown Codebase)
+  <example>
+  user: I'm new to this project, what's the structure?       
+  assistant: [uses Glob tool with pattern="**/package.json" to find project roots]
+  [uses Glob tool with pattern="src/**/*.{ts,tsx}" to understand source layout]
+  [uses LS tool on key directories to see detailed structure]
+  </example>
+
+  ### Example 2: Find Files by Type in Specific Area
+  <example>
+  user: Find all test files in the auth module
+  assistant: [uses Glob tool with pattern="src/auth/**/*.test.ts"]
+  [uses Read tool to examine specific test files]
+  </example>
+
+  ### Example 3: Config File Location (Deterministic)        
+  <example>
+  user: Where is the webpack configuration?
+  assistant: [uses Glob tool with pattern="**/webpack*.{js,ts,json}"]
+  [uses Read tool on the matched config file]
+  </example>
+
+  ### Example 4: Semantic Fallback for Symbol-Based File Lookup
+  <example>
+  user: Find the file that defines \`UserRepository\`        
+  assistant: [uses Glob tool with pattern="*UserRepository*" - no results]
+  [uses Glob tool with pattern="UserRepository" semantic:true]
+  [uses LSP goToDefinition to confirm the symbol location]
+  </example>
+
+  ### Example 5: Parallel Discovery for Entry Points
+  <example>
+  user: What are the main entry points of this application?
+  assistant: [uses Glob tool with pattern="**/index.{ts,js}"]
+  [uses Glob tool with pattern="**/main.{ts,js}"]
+  [uses Glob tool with pattern="**/app.{ts,js}"]
+  [uses Read tool to examine the entry point files]
+  </example>
+
+  ### Example 6: Narrow Down After Broad Results
+  <example>
+  user: Find all TypeScript files in the project
+  assistant: [uses Glob tool with pattern="**/*.ts" - returns 500+ files, truncated]
+  [uses Glob tool with pattern="src/**/*.ts" to focus on source code]
+  [uses Glob tool with pattern="src/core/**/*.ts" to narrow further if needed]
+  </example>
+`;
 
 // src/tools/filesystem/GlobTool/GlobTool.tsx
 import { existsSync as existsSync6, statSync as statSync9 } from "fs";
@@ -8298,7 +8357,7 @@ import { z as z7 } from "zod";
 
 // src/tools/search/GrepTool/prompt.ts
 var TOOL_NAME_FOR_PROMPT3 = "Grep";
-var DESCRIPTION5 = `A powerful search tool built on ripgrep
+var DESCRIPTION5 = `A powerful fast content search tool that works with any codebase size
 
   ## Best Practice
   - Use Grep as a "Scout" to *find* entry points based on text patterns.
@@ -8329,17 +8388,90 @@ var DESCRIPTION5 = `A powerful search tool built on ripgrep
 
   ## Usage Details
   - ALWAYS use Grep for search tasks. NEVER invoke \`grep\` or \`rg\` as a Bash command. The Grep tool has been optimized for correct permissions and access.
-  - Supports full regex syntax (e.g., "log.*Error", "function\\s+\\w+")
-  - Filter files with glob parameter (e.g., "*.js", "**/*.tsx") or type parameter (e.g., "js", "py", "rust")
-  - Path guidance: If the user provides a path, use it directly. If the path is uncertain or model-inferred, confirm with LS/Glob first; otherwise search from the current working directory.
-  - Output modes: "content" shows matching lines, "files_with_matches" shows only file paths (default), "count" shows match counts
-  - Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (use \`interface\\{\\}\` to find \`interface{}\` in Go code)
-  - Multiline matching: By default patterns match within single lines only. For cross-line patterns like \`struct \\{[\\s\\S]*?field\`, use \`multiline: true\`
-  - Semantic search: Set \`semantic: true\` to use LSP workspace symbols when text search yields no results or when you explicitly need symbol-based lookup. The \`pattern\` is treated as the symbol name.
-  - Semantic search is explicit: enable only when normal search has no results or when symbol-level lookup is required
+  - Powered by ripgrep for fast text search with full regex support (e.g., "log.*Error", "function\\s+\\w+")
+  - Pattern syntax: Uses ripgrep - literal braces need escaping (use \`interface\\{\\}\` to find \`interface{}\` in Go code)
+  - Excludes version control directories (.git, .svn, .hg, .bzr) automatically
+  - Includes hidden files by default
+
+  **Path & Scope**:
+  - \`path\` parameter: File or directory to search in. Defaults to current working directory.
+  - \`glob\` parameter: Filter files by glob pattern (e.g., "*.js", "*.{ts,tsx}") - maps to rg --glob
+  - \`type\` parameter: Filter by file type (e.g., "js", "py", "rust", "go", "java") - more efficient than glob for standard types
+  - Path guidance: If user provides a path, use it directly. If uncertain, confirm with LS/Glob first.
+
+  **Output Modes**:
+  - \`files_with_matches\` (default): Returns file paths sorted by modification time
+  - \`content\`: Shows matching lines with line numbers (supports -A/-B/-C context)
+  - \`count\`: Shows match counts per file
+
+  **Context & Pagination**:
+  - \`-B\`, \`-A\`, \`-C\`: Context lines before/after/around matches (requires output_mode: "content")
+  - \`-n\`: Show line numbers (default: true, requires output_mode: "content")
+  - \`head_limit\`: Limit output to first N entries (works across all modes)
+  - \`offset\`: Skip first N entries before applying head_limit
+  - \`multiline\`: Enable multiline mode where . matches newlines (default: false)
+
+  **Case Sensitivity**:
+  - \`-i\`: Enable case-insensitive search
+
+  **Semantic Search**:
+  - \`semantic: true\`: Enable LSP workspace symbol search as fallback when text search yields no results.
+  - \`symbol_type\`: Filter semantic search by symbol type (e.g., "class", "function", "variable"). Requires semantic: true.
+    - When \`symbol_type\` is specified, LSP search replaces (not augments) text search results.
+    - Supported types: file, module, namespace, package, class, method, property, field, constructor, enum, interface, function, variable, constant, struct, event, operator, typeparameter
   - Semantic output format: \`file:line: name (Kind)\` for quick follow-up reads
-  - If LSP is unavailable, fall back to plain text search results
-  - Use Task tool for open-ended searches requiring multiple rounds`;
+  - On success: returns notice "Semantic search: added X results. Next: use LspTool for details."
+  - If LSP is unavailable: returns "Semantic search: LSP unavailable."
+
+  **Result Handling**:
+  - Results are truncated at 20,000 characters if too large
+  - Use Task tool for open-ended searches requiring multiple rounds
+
+  **Typical Usage Examples**:
+
+  Example 1: Exact Error Message Tracing (Deterministic)
+  <example>
+  user: Where does the error "Connection timeout after 30s" come from?
+  assistant: [uses Grep tool with pattern="Connection timeout after 30s"output_mode="content"]
+  [uses Read tool to examine the error source and surrounding context]
+  </example>
+
+  Example 2: Precise Function Definition Lookup (Deterministic)
+  <example>
+  user: Find the implementation of \`calculateCompoundInterest\` function
+  assistant: [uses Grep tool with pattern="calculateCompoundInterest" type="ts"output_mode="content"]
+  [uses Read tool on the matched file to read the full implementation]
+  </example>
+
+  Example 3: Concept Search with Semantic Fallback
+  <example>
+  user: Where is authentication logic implemented?
+  assistant: [uses Grep tool with pattern="auth" type="ts" semantic: true]
+  [uses Read tool to examine the most relevant matches]
+  [uses LSP goToDefinition to trace the core auth flow]
+  </example>
+
+  Example 4: Iterative Narrowing for Broad Patterns
+  <example>
+  user: Find all API route definitions
+  assistant: [uses Grep tool with pattern="router\\.(get|post|put|delete)" type="ts"]       
+  [if too many results: adds path="src/routes" to narrow scope]
+  [uses Read tool to inspect specific route handlers]
+  </example>
+
+  Example 5: Handoff to LSP After Entry Point Found
+  <example>
+  user: Find all usages of the \`PaymentService\` class
+  assistant: [uses Grep tool with pattern="class PaymentService" type="ts"output_mode="content"]
+  [uses LSP findReferences at the class definition location to get all references]
+  </example>
+
+  Example 6: Case-Insensitive Search for Config Values
+  <example>
+  user: Where is the database host configured?
+  assistant: [uses Grep tool with pattern="database.*host|db_host|DB_HOST" -i: true]        
+  [uses Read tool to examine configuration files]
+  </example>`;
 
 // src/tools/search/GrepTool/GrepTool.tsx
 import { isAbsolute as isAbsolute7, relative as relative9, resolve as resolve7 } from "path";
@@ -11926,7 +12058,7 @@ async function createAndStoreApiKey(accessToken) {
       }
       saveGlobalConfig(config2);
       try {
-        const { resetAnthropicClient } = await import("./llm-Q23IAP4O.js");
+        const { resetAnthropicClient } = await import("./llm-T7C6QJWB.js");
         resetAnthropicClient();
       } catch {
       }
@@ -16350,7 +16482,7 @@ async function refreshPluginRuntimeFromInstalls() {
   const existingRoots = getSessionPlugins().map((p) => p.rootDir);
   const dirs = Array.from(/* @__PURE__ */ new Set([...existingRoots, ...installedRoots]));
   if (dirs.length === 0) return [];
-  const { configureSessionPlugins } = await import("./pluginRuntime-C6QS67LQ.js");
+  const { configureSessionPlugins } = await import("./pluginRuntime-WNZS26EV.js");
   const { errors } = await configureSessionPlugins({ pluginDirs: dirs });
   return errors;
 }
@@ -17025,7 +17157,7 @@ async function call(onDone, context) {
     ModelConfig,
     {
       onClose: () => {
-        import("./model-OGMQRRY5.js").then(({ reloadModelManager: reloadModelManager2 }) => {
+        import("./model-GBC2PBVJ.js").then(({ reloadModelManager: reloadModelManager2 }) => {
           reloadModelManager2();
           triggerModelConfigChange();
           onDone();
@@ -25229,7 +25361,7 @@ function useStatusLine() {
 // src/ui/components/PromptInput.tsx
 async function interpretHashCommand(input) {
   try {
-    const { queryQuick: queryQuick2 } = await import("./llm-Q23IAP4O.js");
+    const { queryQuick: queryQuick2 } = await import("./llm-T7C6QJWB.js");
     const systemPrompt = [
       "You're helping the user structure notes that will be added to their PYB.md file.",
       "Format the user's input into a well-structured note that will be useful for later reference.",
@@ -25542,7 +25674,7 @@ function PromptInput({
     if (messages2.length) {
       if (mode === "bash") {
         onQuery(messages2, newAbortController).then(async () => {
-          const { getCwd: getCwd2 } = await import("./state-I4ULG2ZQ.js");
+          const { getCwd: getCwd2 } = await import("./state-MAVHRDNE.js");
           setCurrentPwd(getCwd2());
         });
       } else {
@@ -31928,7 +32060,7 @@ import { homedir as homedir8 } from "os";
 // src/commands/agents/generation.ts
 import { randomUUID as randomUUID6 } from "crypto";
 async function generateAgentWithClaude(prompt) {
-  const { queryModel } = await import("./llm-Q23IAP4O.js");
+  const { queryModel } = await import("./llm-T7C6QJWB.js");
   const systemPrompt = `You are an expert at creating AI agent configurations. Based on the user's description, generate a specialized agent configuration.
 
 Return your response as a JSON object with exactly these fields:
@@ -35539,7 +35671,7 @@ It is critical that you mark tasks as completed as soon as you are done with a t
 # Cognitive Safety & Sensing
 1. **Modification Check**: Before editing, you MUST verify if the change is already present (e.g. use \`grep\` or \`read\`). Do not rely on memory from previous turns.
 2. **Precise Targeting**: For code injection, prefer using LSP to find exact function boundaries, or Read the file to get unique context.
-3. **Artifact Verification**: After completing a complex task, verify the artifacts (e.g. check if files exist using \`ls\`).
+3. **Artifact Verification**: After completing a complex task, verify the artifacts (e.g. check if files exist using \`ls\` or \`glob\`).
 4. **LSP Instinct**: Before modifying any code, you MUST first build structure context (structure tree \u2192 hotspot \u2192 Read). Use \`LSP documentSymbol\` or \`LSP goToDefinition\` only when you have a precise position and need to confirm exact range. Do NOT rely on line numbers from \`read_file\` alone as they may be outdated.
 5. **Atomic Verification**: When editing code, especially in critical or complex files, you should strongly consider setting \`verify: true\` in the \`FileEditTool\`. This enables the tool to automatically detect syntax errors and ROLLBACK changes if they are invalid, preventing you from breaking the build.
 6. **Semantic Search**: When searching for code concepts (e.g. "AuthLogic", "UserHandler") rather than exact filenames, prefer using \`GlobTool\` with \`semantic: true\`. This leverages LSP to find files by their content definitions.
@@ -35576,14 +35708,6 @@ user: is 11 a prime number?
 assistant: Yes
 </example>
 
-<example>
-user: locate where auth token refresh is implemented in a large repo
-assistant: [uses the LS tool to scan top-level structure]
-[uses the Glob tool to find candidate auth-related files]
-[uses the Grep tool to search for token refresh patterns]
-[uses the Read tool to inspect the most likely file]
-</example>
-
 <example>
 user: find all .ts and .tsx files under src/
 assistant: [uses the Glob tool to match files under src/]
@@ -35594,11 +35718,6 @@ user: How many golf balls fit inside a jetta?
 assistant: 150000
 </example>
 
-<example>
-user: delete the temp directory and all logs
-assistant: [uses Delete tool to remove 'temp' directory and all '*.log' files in one call]
-</example>
-
 <example>
 user: list files in the directory src/
 assistant: [uses the LS tool to list files and sees foo.c, bar.c, baz.c]
@@ -35636,8 +35755,8 @@ When making changes to files, first understand the file's code conventions. Mimi
 
 ${includeCodingInstructions ? `# Doing tasks
 The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- Use TaskCreate to plan multi-step work and TaskUpdate to track progress; use TaskList/TaskGet to review
-- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
+- Use TaskCreate VERY frequently to plan multi-step work required 2 or more distinct steps and TaskUpdate to track progress; use TaskList/TaskGet to review
+- Use the available search tools\uFF08e.g., Glob\u3001Grep\u3001LSP\u3001LS\uFF09 to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
 - Implement the solution using all tools available to you
 - Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
 - VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (eg. npm run lint, npm run typecheck, ruff, etc.) if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to ${PROJECT_FILE} so that you will know to run it next time.
@@ -35647,20 +35766,22 @@ NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTAN
 ` : ""}
 
 # Tool usage policy
-- **Code Analysis & Exploration Priority**:For **complex** codebase exploration tasks (e.g., searching across 3+ directories, requiring multiple search iterations, or investigating cross-module patterns), prefer using the Task tool with Explore subagent. This isolates exploration context in a separate transcript.For simple tasks (reading known files, single-pattern searches), use Ls/Read/Glob/Grep directly for faster results.
-- **File Search Priority**:When doing file search, prefer to use the Task tool for open-ended, multi-step exploration to reduce context usage. For known paths or small scopes, prefer Ls/Lsp/Read/Glob/Grep directly.
-- **File System Exploration Priority**:For file system exploration, decide based on intent: if you need global structure/entry points, prefer LS first; if you have keywords or fuzzy paths, prefer Glob first. If results are too broad, use LS to narrow structure or combine with Grep/LSP. Only use Bash for executing scripts or binaries.
 - You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency. However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
+- **LS vs Glob "dir/*"**: LS provides complexity stats (directory/file ratio, max depth) to guide strategy; Glob "dir/*" is faster but no stats. Use LS when you need structural insights; use Glob for quick one-level checks.
 - If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks.
 - It is always better to speculatively read multiple files as a batch that are potentially useful.
 - It is always better to speculatively perform multiple searches as a batch that are potentially useful.
 
+
 # Cognitive Search Strategy
 1. **Concept Search**: WHEN searching for high-level concepts (e.g., "Auth Logic", "Payment Flow") OR when you are uncertain about exact naming, you MUST use \`semantic: true\` in Grep/Glob tools. This activates the LSP Workspace Symbol search which is resilient to typos and fuzzy matches.
    - Example: \`GrepTool(pattern: "AuthFeatr", semantic: true)\` will find "AuthFeature".
    - Example: \`GlobTool(pattern: "tests", semantic: true)\` will find test files based on project structure.
 2. **Exact Identifier**: WHEN you know the precise class/function name (e.g., "UserProfile", "initDatabase"), use standard Grep/Glob without \`semantic\` flag.
 3. **Exploration**: If standard search returns 0 results, AUTOMATICALLY retry with \`semantic: true\`.
+4. **File System Exploration Priority**:For file system exploration, decide based on intent: if you need global structure/entry points, prefer LS or Glob "dir/*" first; if you have keywords or fuzzy paths, prefer Glob first. If results are too broad, use LS or Glob "dir/*" to narrow structure or combine with Grep/LSP. Only use Bash for executing scripts or binaries.
+5. **Code Analysis & Exploration Priority**:For codebase exploration tasks (e.g., searching across 2 or more directories, requiring multiple search iterations, or investigating cross-module patterns), prefer using the Task tool with Explore subagent. This isolates exploration context in a separate transcript.For simple tasks (reading known files, single-pattern searches), use Glob/Grep/Ls/Read/Lsp directly for faster results.
+6. **File Search Priority**:When doing file search, prefer to use the Task tool for open-ended, multi-step exploration to reduce context usage. For known paths or small scopes, prefer Ls/Lsp/Read/Glob/Grep directly.
 
 # Path Fragmentation Strategy
 - Root -> Core Directory -> Secondary Modules