update instructions to emphasize deletion comments

Author: charleslien

backend/src/__tests__/__snapshots__/tools.test.ts.snap

@@ -499,6 +499,8 @@ Indicate the location and nature of the modifications (additions and deletions)
 
 Make sure that you preserve the indentation and code structure of exactly how you believe the final code will look like (do not output lines that will not be in the final code after they are merged).
 
+##### **IMPORTANT** Deletion Comments
+
 **CRITICAL FOR DELETIONS** If you plan on deleting a section, you MUST provide a comment giving the relevant context such that the code is understood to be removed. This is REQUIRED for the fast-apply model to understand what to delete.
 
 Examples:
@@ -518,7 +520,9 @@ Block 3
 // rest of code
 \`\`\`
 
-**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing **anything**: single lines, code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+
+Merely omitting the code block may or may not work. In order to guarantee the deletion of the code, you must include a deletion comment.
 
 #### Additional Info
 
@@ -547,17 +551,19 @@ Example 1 - Simple file creation:
 Example 2 - Editing with placeholder comments:
 <write_file>
 <path>foo.ts</path>
-<content>// no change to imports
+<content>// ... existing code ...
 
 function foo() {
   console.log('foo');
   for (let i = 0; i < 10; i++) {
     console.log(i);
   }
   doSomething();
+
+  // Delete the console.log line from here
 }
 
-// rest of code</content>
+// ... existing code ...</content>
 </write_file>
 
 ### str_replace
@@ -1047,6 +1053,8 @@ Indicate the location and nature of the modifications (additions and deletions)
 
 Make sure that you preserve the indentation and code structure of exactly how you believe the final code will look like (do not output lines that will not be in the final code after they are merged).
 
+##### **IMPORTANT** Deletion Comments
+
 **CRITICAL FOR DELETIONS** If you plan on deleting a section, you MUST provide a comment giving the relevant context such that the code is understood to be removed. This is REQUIRED for the fast-apply model to understand what to delete.
 
 Examples:
@@ -1066,7 +1074,9 @@ Block 3
 // rest of code
 \`\`\`
 
-**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing **anything**: single lines, code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+
+Merely omitting the code block may or may not work. In order to guarantee the deletion of the code, you must include a deletion comment.
 
 #### Additional Info
 
@@ -1095,17 +1105,19 @@ Example 1 - Simple file creation:
 Example 2 - Editing with placeholder comments:
 <write_file>
 <path>foo.ts</path>
-<content>// no change to imports
+<content>// ... existing code ...
 
 function foo() {
   console.log('foo');
   for (let i = 0; i < 10; i++) {
     console.log(i);
   }
   doSomething();
+
+  // Delete the console.log line from here
 }
 
-// rest of code</content>
+// ... existing code ...</content>
 </write_file>
 
 ### str_replace
@@ -1595,6 +1607,8 @@ Indicate the location and nature of the modifications (additions and deletions)
 
 Make sure that you preserve the indentation and code structure of exactly how you believe the final code will look like (do not output lines that will not be in the final code after they are merged).
 
+##### **IMPORTANT** Deletion Comments
+
 **CRITICAL FOR DELETIONS** If you plan on deleting a section, you MUST provide a comment giving the relevant context such that the code is understood to be removed. This is REQUIRED for the fast-apply model to understand what to delete.
 
 Examples:
@@ -1614,7 +1628,9 @@ Block 3
 // rest of code
 \`\`\`
 
-**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing **anything**: single lines, code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+
+Merely omitting the code block may or may not work. In order to guarantee the deletion of the code, you must include a deletion comment.
 
 #### Additional Info
 
@@ -1643,17 +1659,19 @@ Example 1 - Simple file creation:
 Example 2 - Editing with placeholder comments:
 <write_file>
 <path>foo.ts</path>
-<content>// no change to imports
+<content>// ... existing code ...
 
 function foo() {
   console.log('foo');
   for (let i = 0; i < 10; i++) {
     console.log(i);
   }
   doSomething();
+
+  // Delete the console.log line from here
 }
 
-// rest of code</content>
+// ... existing code ...</content>
 </write_file>
 
 ### str_replace
@@ -2143,6 +2161,8 @@ Indicate the location and nature of the modifications (additions and deletions)
 
 Make sure that you preserve the indentation and code structure of exactly how you believe the final code will look like (do not output lines that will not be in the final code after they are merged).
 
+##### **IMPORTANT** Deletion Comments
+
 **CRITICAL FOR DELETIONS** If you plan on deleting a section, you MUST provide a comment giving the relevant context such that the code is understood to be removed. This is REQUIRED for the fast-apply model to understand what to delete.
 
 Examples:
@@ -2162,7 +2182,9 @@ Block 3
 // rest of code
 \`\`\`
 
-**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+**YOU MUST ALWAYS INCLUDE DELETION COMMENTS** when removing **anything**: single lines, code blocks, functions, variables, or any other code elements. The fast-apply model cannot understand deletions without these explicit comments.
+
+Merely omitting the code block may or may not work. In order to guarantee the deletion of the code, you must include a deletion comment.
 
 #### Additional Info
 
@@ -2191,17 +2213,19 @@ Example 1 - Simple file creation:
 Example 2 - Editing with placeholder comments:
 <write_file>
 <path>foo.ts</path>
-<content>// no change to imports
+<content>// ... existing code ...
 
 function foo() {
   console.log('foo');
   for (let i = 0; i < 10; i++) {
     console.log(i);
   }
   doSomething();
+
+  // Delete the console.log line from here
 }
 
-// rest of code</content>
+// ... existing code ...</content>
 </write_file>
 
 ### str_replace