Sync milestones with 'closed' state has unexpected behavior

[linc]

Scenario: I have some milestones in the future that were incorrectly made & synched. We now want to close them across all repos.

• Closing the milestones in the source ("from") repo and syncing does nothing, because they are no longer in state open (the default $state) and thus not checked.
• Autoclose does not work, because they are in the future.
• Running the sync with state closed creates new, open milestones on the target repos for every closed milestone on the source repo. This doesn't make a lick of sense.

So, there is currently no way to forcibly close milestones with this tool. And there is an action that seems like it would accomplish that, but does something much worse instead.