The solution I have for making sure the history stays in tact is to commit in 2 separate revisions. One that only renames files, and another that only modifies the files after they've been renamed. Although the file renames will show up as adds / deletes in this web interface, they should be renames on the server. I can verify locally that git log --follow shows history for every file.
So, in summary - this change doesn't actually need to be reviewed, it's just here in case you want to apply these patches locally in succession to test the patch. The deleted and added files have identical content.