Import of sites does not work with the new drush call mechanism.

In previous releases, import would be triggered by the verification of a platform.
If the platform returned a site that we had not seen yet, we would generate a new dummy site node and create the import task.

We would call drush import with whatever arguments we already had, and it would fill in the rest of them from the settings.php and save it to the site's drushrc.php.

With the multi-server work going on in HEAD the model is turned around a bit. We need more information about the site before being able to call import or verify on it, because we need to be able to generate a working site alias record for it.

The most important part here is that we have no way of determining what the site's database server is from simply seeing it's name in a list retrieved from the platform. This would mean that either the platform verify would have to bootstrap all the sites underneath it, or we would have to work out a different plan.

So you can't do drush @site.com provision-import before you;ve done the drush provision-save @site.com, and you can't do the provision-save before you do the provision-import.