I don't want to make it distinguishable. The self-contained phar version of zftool should only be used for deployment. After that, you should have a `zftool` module in `vendor/` of your application. The recommended way to run the app should then be `./zf` or `bin/zf` instead of `zf`. 

Additionally, we could throw in a simple file_exists into the self-contained, global version so when it detects an attempt to run `zf` inside existing app root, that contains other copy of zftool, it'd use the other one instead (that makes it consistent, circumvents neebs confusion related to having dot-slash or not having it). 

I'm also still more in favor of shortcuts, such as that `./zf` instead of `php public/index.php` or `php somewhere/zftool.phar` or some other verbose commands. My apps usually have tens of console commands that I use regularly. That's what hashbang has been created for and that's how we use many other scripts (including `composer` global install or `drush`)