paket dependency order importance

Description

The order of dependencies in a paket.dependency file is important when using strategy:min
Even though the docs state:
Note, however, that all direct dependencies will still get their latest matching versions, no matter the value of the strategy option. If you want to influence the resolution of direct dependencies then read about the lowest_matching option. this is NOT always the case.

Repro steps

Create a repo with dependency of

source https://api.nuget.org/v3/index.json
framework: auto-detect
storage: none
strategy: min

nuget Castle.Core
nuget Castle.Windsor

Run a paket install, everything looks good, you have castle.core with the latest version.

Flip the 2 dependencies round.

Castle.Core is downgraded to the miniumum required by Castle.Windsor

Expected behavior

Order is not important in a dependencies file

Actual behavior

Order is important in a dependencies file

Known workarounds

Get things in the right order...whatever that may be ;)

Reproduce the behavior with the two paket.dependency files shown and run paket install using strategy:min. Trace dependency resolution for Castle.Core and Castle.Windsor, then verify that reversing their declarations produces the same resolved versions and that the documented direct-dependency behavior remains correct.