I suspect when they "repaired their scanning engine" that refers to the database file that contains the virus/malware/Potentially Unwanted Program signatures used by ClamXAV to detect/identify the viruses/malware/Potentially Unwanted Programs present in the system it is protecting. Normally those are updated at regular intervals ranging from every few hours to weekly depending on the particular application and user preferences. (I use MalwareBytes Premium and have it set to check every three hours for updated signature files.) Given a new exploit appears every eleven seconds, on the average, those files are highly dynamic, and it would not be surprising that a version could easily become corrupt or damaged and have to repaired.
Thanks for the explanation, joemikeb. Whenever I launch ClmXAV, the first thing it does, of course, is to update its malware database. I then run a complete scan of my entire internal SSD. It does take some time, so I guess it's possible the updated database could already be "old", per se.