What was expected?:
Adding an asset or folder to a project, publishing the change, and then restoring clean to a commit before that change should result in a clean local project as it was before the new asset or folder was added.

What actually happened?:
Technically correct behavior occurs, but as part of the process, it orphans the .meta file(s) for the newly added asset(s) and the cleanup of it produces console warnings.

How do you reproduce this problem?:
1) Add a new asset
2) Publish change
3) Click "go back" to second to last revision
4) Update to lastest commit
5) Restart Unity
6) Check to see there are no changes pending, as expected, but you got some console warnings along the way complaining about orphaned meta files.

Discovered on the 2017.2.0f1 RC1 build.