Success messages versus actual state

rerere.autoupdate stages a replayed resolution before anyone checks it hit the right file

A dev.to write-up pairs each git success message with the state it actually leaves behind, and on git 2.39.5 the gap shows up in the index, then again in a fixup! commit that survived a rebase, and once more in a pull request GitHub called mergeable.