add write tool formatters

[LasmarKhalifa]

Closes #1025

[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
• add write tool formatters #1017 👈 (View in Graphite)
• 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]

write formatter — one inconsistency with the sibling formatters.

[mathiusj]

format_write has no bare-name fallback and interpolates path untruncated — unlike every sibling. format_bash/format_ls/format_read degrade to "BASH"/"LS"/"READ" when the key is absent and run path through truncate. This line renders unconditionally, so no-args produces WRITE "" (+0 lines) (double space, empty quotes), and a long path blows the one-line goal since it isn't truncated. Suggest guarding the bare case and wrapping path in truncate to match the others.

[LasmarKhalifa]

Added the fallback for nil paths, but the path should not be truncated. Some tools truncate the command or other values, such as BASH and LS, but the path should remain fully present so that users can easily access the items that were modified. This mirrors the Claude side of tool formatters.