The fileset being used for the board is a mixture of 3.2.2, 3.2.5 and 3.2.7 files + some files are a version I haven't identified yet and are probably modified. Some files are 3.2.7 files which haven't been changed since 3.2.5 so I would expect them to be exactly the same, except they aren't: they have extra bytes.
Also: there are way more extensions installed than mentioned. One of them being an old version of Lightbox, and the s9e is also way past its date of expiry .
The good news is that the whole vendor directory is clean 3.2.7 version (probably because autoupdate didn't touch that).
This board is in a similar condition as one I started on in January, first getting it back to work on 3.2.4 and only recently managed to completely identify and clean the original files in order to identify the real modifications so as to be able to update.
It's not the first autoupdated board I've been fixing but I have a feeling it's going to be the last one because in some (many) cases autoupdate obscurifies all (on purpose) modifications by modifying files which didn't contain any modifications in the first place. I've seen autoupdated boards without the unnecessary file modifications (1 extra byte per carriage return I think) so it does do its job properly sometimes (probably something to do with the host configuration).
The answer to this would have immediately confirmed my " Damn! another autoupdate miscarriage" fear.
Time for (late) lunch but first add "autoupdate" to my list of offensive words.