what nuget packages are needed for getting Find 10 up and running in commerce manager?

Exactly what packages are needed on the commerce manager site to get it up and running with Find 10?

We are starting with packages EPiServer.CommerceManager 9.1 and it pulls in EPiServer.Commerce.Core 9.1 which in turn pulls in EPiServer.CMS.Core and related packages.

Now the commerce manager can start and everything seems to work just fine.

Then we try to add EPiServer.Commerce.FindSearchProvider 8.10.0 so we can configure a search provider for commerce which in turn pulls in a lot of packages. Now commerce manager can no longer start:

-----

While loading .NET types from "EPiServer.Find.UI" the following error(s) was reported:

    - System.IO.FileNotFoundException: Could not load file or assembly 'EPiServer.Cms.Shell.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' or one of its dependencies. The system cannot find the file specified.
File name: 'EPiServer.Cms.Shell.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


While loading .NET types from "EPiServer.Find.Blocks" the following error(s) was reported:

    - System.IO.FileNotFoundException: Could not load file or assembly 'EPiServer.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' or one of its dependencies. The system cannot find the file specified.
File name: 'EPiServer.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].