Improved diff editing use consistency

[hannesrudolph]

…ion apply_diff before write_to_file

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• My code follows the patterns of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

Related Issues

Reviewers

---

Important

Reorder tool groups to prioritize apply_diff over write_to_file and update related instructions in capabilities.ts, modes.ts, and rules.ts.

• Tool Group Reordering:
  • In tool-groups.ts, reorder edit group tools to prioritize apply_diff over write_to_file.
  • Update modes.ts to reflect the new order in tool group comments.
• Instruction Updates:
  • In capabilities.ts, update example usage to prioritize apply_diff over write_to_file when diffStrategy is true.
  • In rules.ts, adjust instructions to prefer apply_diff over write_to_file for existing file changes.

^{This description was created by for 24d5280. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6225994

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mrubens]

🙏