add edit tool formatters

[LasmarKhalifa]

Closes #1026

[LasmarKhalifa]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• add ls tool formatters #1021
• add find tool formatters #1020
• add grep tool formatters #1019
• add edit tool formatters #1018 👈 (View in Graphite)
• add write tool formatters #1017
• add read tool formatters #1016
• add bash tool formatters #1014
• restructure Pi tool formatting into per-method dispatch with generic fallback #1012
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[mathiusj]

edit formatters look good. Two small things.

[mathiusj]

|| [] only guards nil — if :edits ever arrives as a non-Array (e.g. a String or a single Hash), .length either silently returns the wrong count (char count for a String) or raises. Given this is display-only, I wouldn't add validation here; the clean fix is a rescue→format_unknown at the dispatch site in #1012 (commented there). Just flagging so it's a conscious choice rather than an assumption. Also note EDIT #{path} interpolates the path untruncated, so a long path blows past the one-line goal the comments state.

[mathiusj]

Readability nit: the result formatter reads @input[:path] while the call formatter (same field) reads arguments[:path]. Both correct — @input is the resolved call's args in the result context, arguments is the call's own ivar — but the naming divergence across the two files costs a beat to reconcile. A one-line comment noting they're deliberately different objects would help future readers.