The finder index component page display a message about the content plugin not being enabled. This is despite all plugin components displayed in the Extension - Plugins section being marked as enabled. Looking at the code it is checking that plg_content_finder is enabled. Looking in the database itself in the #__extentions table I can see that it is not enabled. Enabling it in the database directly removes the message (as expected.) What is interesting is that the problem exists in the upgrade and the full release, and even if you have the message the contents still get indexed and displayed (see problem with the display next.)
The finder component works as long as there is a menu item created. Attempts to use it without the menu item i.e. as a module only have been mixed. Sometimes I get a 'page not found' and at other times I get a strangely formatted search page with the results highlighted and spaces in between each letter. Very strange. Let us hope that the release version is more stable.
The other enhancements are not quite as useful (to us at least.)