Moving additional files using the default path naming scheme in Picard can cause data loss. If there is an existing file in the destination with the same name (or files with identical names in the source folders), it will overwrite the existing file.

See the pre/post tagging screenshots in: https://community.metabrainz.org/t/feature-request-avoid-overwriting-additional-files/486177.

Each disc folder in the pre-tagged tree has its own set of cover/cue/log files. In the post-tagged tree, there is only one set of cover/cue/log files.

To avoid this, a similar mechanism to the one for moving music files seems reasonable: check if there are name collisions, and if so, add a unique ending. The one hiccup might be when log.log and log(1).log correspond to disc1 and disc2, which might be slightly illogical, but at least the data is not lost.