How can I remove an unstaged file without altering the repository?

I recently cloned a GitHub Repository to my computer (Windows 11 Dell). The cloning process went fine, but when I checked the status it shows two of the files were deleted and are waiting to commit the changes to the repository.

$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        deleted:    gfx/interface/goals/TRM_Army.png
        deleted:    gfx/interface/goals/TRM_Navy.png

The issue is here is that I cannot update this cloned repository as long as those files are present, and nothing I have tried has been able to remove them.

I've tried:

• Normal discard from GitKraken (my default program)
• git reset
• git checkout
• git restore
• Stashing the files
• git clean
• Deleting and re-cloning the repository
• Uninstalling and Reinstalling Git
• git reflog
• Case-Sensitivity
• git rm
• git config

All of these methods have failed to produce results. The best I've been able to do is unstage the files, but this is not helpful as I still cannot delete them. I have checked git diff but there are no differences that it can detect, only git status is detecting them. The error is being detected on four different programs: Git Bash, Git GUI, GitHub Desktop and GitKraken (though Git GUI and Git Bash don't show the errors anymore if they were unstaged). I am not able to commit the changes as it would delete the files from the repository, and I do not own nor do I have permission to alter the repository. Is there a way to remove these phantom deletions without altering the repository?

Git GUI is showing this:

deleted file mode 100644
Binary files a/gfx/interface/goals/TRM_Navy.png and /dev/null differ

TL;DR: I have phantom 'changes' that were not made but I cannot remove and I am not able to alter the repository in anyway from its' current condition. No solution that I have found so far has worked.

Issue appears to be on the repository's end, as it looks like the repository has duplicated the problematic files, with two copies of each one, varying only by case. I've messaged the repository about the glitched files, so hopefully they'll fix it at some point.