pybao-cli 1.5.49 → 1.5.50

package/dist/{chunk-UEF22EAA.js → chunk-FNDIHEBT.js}

@@ -3,13 +3,13 @@ const require = __pybCreateRequire(import.meta.url);
 import {
   getSettingsFileCandidates,
   loadSettingsWithLegacyFallback
-} from "./chunk-JJNZ7WEP.js";
+} from "./chunk-CNBKKQSV.js";
 import {
   getSessionPlugins
 } from "./chunk-BJSWTHRM.js";
 import {
   getTheme
-} from "./chunk-AKDLTQJZ.js";
+} from "./chunk-EY3ZOE75.js";
 import {
   addMcprcServerForTesting,
   getCurrentProjectConfig,
@@ -19,13 +19,13 @@ import {
   safeParseJSON,
   saveCurrentProjectConfig,
   saveGlobalConfig
-} from "./chunk-NYRCQC7E.js";
+} from "./chunk-CNW45NOZ.js";
 import {
   PRODUCT_COMMAND,
   PRODUCT_NAME,
   getCwd,
   logMCPError
-} from "./chunk-ZBUV2OFZ.js";
+} from "./chunk-UJRT7VK2.js";
 
 // src/services/mcp/client.ts
 import { existsSync as existsSync2, readFileSync as readFileSync2 } from "fs";
@@ -1036,7 +1036,7 @@ Usage:
 Notes:
 - The edit will FAIL if the SEARCH block matches multiple locations(ambiguous). Provide more context.
 - To delete code, leave the REPLACE section empty.
-- To create a new file, use an empty SEARCH block with the desired content in REPLACE.
+- To create a new file with Edit, use an empty SEARCH block with the desired content in REPLACE only in efficiency-focused scenarios (for example, when you are already performing a multi-block edit workflow and adding one small new helper file in the same operation).
 - ALWAYS prefer editing existing files. NEVER write new files unless explicitly required.
 - For Jupyter Notebooks (.ipynb), use the NotebookEditTool instead.
 
@@ -1075,12 +1075,49 @@ var TOOL_NAME4 = "Write";
 var DESCRIPTION4 = "Write a file to the local filesystem.";
 var PROMPT3 = `Writes a file to the local filesystem.
 
-Usage:
-- This tool will overwrite the existing file if there is one at the provided path.
-- If this is an existing file, you MUST use the ${TOOL_NAME2} tool first to read the file's contents. This tool will fail if you did not read the file first.
-- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
-- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
+## Best Practice
+- **Write vs Edit**: Use this tool when you need to create a new file or fully replace a file's content.
+- **Primary Role**: This is the default tool for new file,parent directories creation and full-file replacement.
+- **Workflow**: Locate path (Glob/Grep) -> Read existing file with ${TOOL_NAME2} when applicable -> Write full target content.
+- **Directory Handling**: If parent directories do not exist, this tool creates them automatically. Do NOT use Bash mkdir for this.
+
+## When NOT to Use Write Tool
+- **Partial updates**: If you only need to change a small section, prefer Edit instead of replacing the entire file.
+- **Unread existing file**: Do NOT overwrite an existing file unless it has been read first with ${TOOL_NAME2}.
+- **Unnecessary new files**: ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
+- **Unrequested docs**: NEVER proactively create documentation files (*.md) or README files. Only create them when explicitly requested by the User.
+
+## Usage Details
+- The file_path parameter must be an absolute path, not a relative path.
+- This tool overwrites existing files at the provided path.
+- For existing files, this tool enforces a read-before-write safety check using ${TOOL_NAME2}.
+- For new files, this tool creates missing parent directories automatically.
+- The content parameter should be the complete desired final file content.
+- Preserve repository conventions (line endings, encoding, and formatting) in the written content.
 - Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.
+
+## Typical Usage Examples
+### Example 1: Create a New File in Nested Directory
+<example>
+ user: Create src/features/auth/config/defaults.ts with these defaults...
+ assistant: [uses Glob/Grep to confirm target area and naming conventions]
+ [uses Write with file_path as absolute path under src/features/auth/config/defaults.ts]
+ [Write auto-creates missing parent directories]
+</example>
+
+### Example 2: Replace Entire Existing File Safely
+<example>
+ user: Rewrite this config file completely with the new schema
+ assistant: [uses ${TOOL_NAME2} to read the existing file first]
+ [uses Write to replace the whole file content]
+</example>
+
+### Example 3: Avoid Write for Small Localized Change
+<example>
+ user: Change only one import line in this file
+ assistant: [uses ${TOOL_NAME2} to inspect file]
+ [uses Edit for localized update instead of Write]
+</example>
 `.trim();
 
 // src/tools/filesystem/GlobTool/prompt.ts
@@ -1652,6 +1689,7 @@ Usage notes:
     - Symbol navigation: Use ${TOOL_NAME7} (NOT ctags/gtags)
     - Read files: Use ${TOOL_NAME2} (NOT cat/head/tail)
     - Edit files: Use ${TOOL_NAME3} (NOT sed/awk)
+    - Create directories/files for content writing: Use ${TOOL_NAME4} directly (NOT mkdir/touch first)
     - Write files: Use ${TOOL_NAME4} (NOT echo >/cat <<EOF)
     - Delete files: Use Delete (NOT rm/rmdir/del). Example: Delete({ file_paths: ["/path/to/file"] })
     - Communication: Output text directly (NOT echo/printf)