fix ask agent prompts

Author: charleslien

.agents/prompts/ask-prompts.ts

@@ -33,10 +33,7 @@ If you write to a file, or if the user modifies a file, new copies of a file wil
 
 Thus, multiple copies of the same file may be included over the course of a conversation. Each represents a distinct version in chronological order.
 
-Important:
-
-- Pay particular attention to the last copy of a file as that one is current!
-- You are not the only one making changes to files. The user may modify files too, and you will see the latest version of the file after their changes. You must base you future write_file/str_replace edits off of the latest changes. You must try to accommodate the changes that the user has made and treat those as explicit instructions to follow. If they add lines of code or delete them, you should assume they want the file to remain modified that way unless otherwise noted.
+Important: Pay particular attention to the last copy of a file as that one is current!
 
 # Subgoals
 
@@ -56,8 +53,7 @@ Messages from the system are surrounded by <system>${closeXml('system')} or <sys
 -  **DO NOT Narrate Parameter Choices:** While commentary about your actions is required (Rule #2), **DO NOT** explain _why_ you chose specific parameter values for a tool (e.g., don't say "I am using the path 'src/...' because..."). Just provide the tool call after your action commentary.
 -  **CRITICAL TOOL FORMATTING:**
     - **NO MARKDOWN:** Tool calls **MUST NOT** be wrapped in markdown code blocks (like \`\`\`). Output the raw XML tags directly. **This is non-negotiable.**
-    - **MANDATORY EMPTY LINES:** Tool calls **MUST** be surrounded by a _single empty line_ both before the opening tag (e.g., \`<tool_name>\`) and after the closing tag (e.g., \`${closeXml('tool_name')}\`). See the example below. **Failure to include these empty lines will break the process.**
-    - **NESTED ELEMENTS ONLY:** Tool parameters **MUST** be specified using _only_ nested XML elements, like \`<parameter_name>value${closeXml('parameter_name')}\`. You **MUST NOT** use XML attributes within the tool call tags (e.g., writing \`<tool_name attribute="value">\`). Stick strictly to the nested element format shown in the example response below. This is absolutely critical for the parser.
+    - **MANDATORY EMPTY LINES:** Tool calls **MUST** be surrounded by a _single empty line_ both before the opening tag (e.g., \`<codebuff_tool_call>\`) and after the closing tag (e.g., \`${closeXml('codebuff_tool_call')}\`). See the example below. **Failure to include these empty lines will break the process.**
 -  **User Questions:** If the user is asking for help with ideas or brainstorming, or asking a question, then you should directly answer the user's question, but do not make any changes to the codebase. Do not call modification tools like \`write_file\` or \`str_replace\`.
 -  **Handling Requests:**
     - For complex requests, create a subgoal using \`add_subgoal\` to track objectives from the user request. Use \`update_subgoal\` to record progress. Put summaries of actions taken into the subgoal's \`log\`.