Enabling LFS tracking for an existing image file breaks diff between the pre-LFS and post-LFS commits

Summary

If you have image files that are not LFS-tracked inside a repo, then enable LFS tracking, the commits immediately before and after enabling LFS tracking will show a broken "diff to previous" state.

Steps to Reproduce

1. Create an empty repo with a test image
2. Modify the image and push to repo
3. Confirm image diffing works
4. Enable LFS tracking for the image and push to the repo
5. Confirm image diff is broken between the pre-LFS and post-LFS commit
6. Modify the image again and push to repo
7. Confirm image diff works again

Expected Results

Image diff continues to work

Actual Results

Between the transitional (pre-LFS and post-LFS) commits, Bitbucket appears to diff the previous image with the text pointer file, resulting in a broken image: