From prune documentation:
Multiple
-keepoptions must be sorted by theirmvalues in decreasing order.
They must be. Why does not duplicacy sort them internally then? Why give a user a chore and opportunity to make mistakes?
Unsorted configuration won’t work: out of order keep parameters wont have any effect. But their presence indicates user wanted them. Duplicacy shall never ignore input. It shall either fail to accept malformed input, or fix it for the user when it’s absolutely sure the fix is correct. In case of prune sorting keep parameters is always correct. Therefore duplicacy shall always do that.