Confirmed: same inode (604044) — it's one physical file with two name forms surfaced by the case-insensitive FS. But git tracks both (case-sensitive index): 158 tracked vs 157 on disk. So git thinks there are two files that map to one real file — a classic case-collision in the git index. That's the true wedge. The clean fix: remove the mixed-case (uppercase) path from git's index, keeping the lowercase canonical one (which matches what my new script now produces). Let me identify all such tracked pairs and drop the uppercase variants from git.