It looks like Recreate beats Repair, not only because of paranoia (we’ll have to figure out how to either obtain a code solution or an advice solution for that – never running Repair isn’t practical, plus it’s being enhanced), but because when I tried to set up this situation by copying an old database over a current one, Repair failed:
Failed to accept new index file: duplicati-i12c3a7d045f9433c9e9ea9e9b49c62d1.dindex.zip, message: Volume duplicati-b559c362a31984483b5a7c4d7cc520c19.dblock.zip has local state Deleting
System.Exception: Volume duplicati-b559c362a31984483b5a7c4d7cc520c19.dblock.zip has local state Deleting
and beyond just tripping over itself, it also “solved” inconsistency by deleting destination to fit its own record, which is similar to your concern on #3416. --dry-run would have caught this (maybe after some deciphering).