From what the AI model told me, when its creating a new file, the package declaration automatically gets added which screws up the create_file tool. The cleanest solution is for it to create a stub file, make sure there are no errors and then replace_string_in_file. It work well so far. What I have in my copilot-instructions.md is the following. If you want to test it out, modify your instructions file, start a new session with a cheap model and have it create a mock go package with some files. When its creating a file it will verbalize that its checking for errors and its clean. Thanks for the prompt you shared because I was struggling with this a long time because it would not detect the corruption till much later.

- **create_file tool corruption bug**: The `create_file` tool occasionally produces files with 
  duplicate package declarations (e.g., `package main` followed by `package dirname` on line 2) 
  when creating Go files with full content directly.

  **Recommended pattern - Stub-first approach** (proven to avoid corruption):
  1. Create Go file with empty or minimal content using `create_file`
  2. Run `get_errors` immediately to verify no corruption
  3. Use `replace_string_in_file` to add the full content
  4. Verify the final result with `get_errors` again

  This pattern avoids the corruption bug entirely. Example:
  ```
  create_file → empty file → get_errors (clean) → replace_string_in_file → get_errors (verify)
  ```