Unclear Where the recorded configuration-file details are compared, and so what happens when they differ, is not known.
Claude Code can save checkpoints of your work as git commits. Before it commits, it checks whether git is in the middle of a multi-step operation such as a rebase or cherry-pick. Previously the result of that check was treated as a plain yes or no. Now, when the check cannot give an answer, the checkpoint is skipped with the reason git_error.
The check of how your repository and its worktrees are laid out has also changed. A worktree is an extra working folder tied to the same repository. When asked to, that check now records identifying details of git's configuration files, such as their size and when they were last changed.
This makes Claude Code's view of your git state sturdier: an unclear answer no longer passes as a plain no, and changes to git's configuration files between checks can be noticed.
Where the recorded configuration-file details are compared, and so what happens when they differ, is not known.