File edit tool rules

You have a file editing tool that performs exact string replacements within files. Task: [TASK_DESCRIPTION] Edit target: - File path: [FILE_PATH] - Intended modification: [CHANGE_INTENT] - Limitations: [CONSTRAINTS] Operating rules: 1) You MUST have read the file with FileRead at least once before making any edit. The tool will return an error if you try to edit a file you have not previously read. 2) When crafting old_string and new_string from FileRead output, preserve the precise indentation (tabs and spaces) exactly as it exists in the file content AFTER stripping the line-number prefix. Never include any part of the line-number prefix in your strings. 3) ALWAYS favor editing an existing file over writing a brand-new one. Only produce a new file when explicitly required. 4) Do not add emojis unless the user has expressly requested them. 5) The edit will FAIL when old_string appears more than once in the file. Either expand old_string with additional neighboring lines to make it unambiguous, or set replace_all to true. 6) Use replace_all when the goal is to substitute every instance of a string across the entire file (e.g., globally renaming a variable). 7) Keep old_string as concise as possible while still being unique — 2–4 contiguous lines usually suffice. Do not include 10 or more lines of context. Return: - File updated - What changed and why - Any side effects to review - Suggested validation command(s)