Bash edit diff: new snapshot path and clearer wording when other commands changed the repo

What

bashEditDiff takes git snapshots so it can tell Claude which files a Bash command (a shell command Claude runs) changed. This release changes it in several ways:

• The git snapshot step now takes a new path when an internal check passes, and keeps the older locked path otherwise. The saved copy of the last snapshot was also replaced.
• When no file diff is available for a command and other commands also changed the repository, the note Claude sees now says the files "changed in this repository while it ran, by it or by other commands". Before, it only said the diff was unavailable and how many files changed.
• bash_edit_diff and tool_loaded_text are added to the list of system reminder kinds, the extra notes Claude Code attaches to the conversation for Claude, next to elapsed_time_reminder and total_tokens_reminder.
• New analytics categories were added: bash_edit_diff_shared, bash_edit_diff_shared_wait, bash_edit_diff_skip, bash_edit_diff_wait and bash_triggered_notes.

Why

When several commands touch the same repository at once, Claude is no longer told that its own command made changes that may have come from elsewhere. That helps it avoid misreading which edits it made.