(Sorry about the length of this post. As you alluded, other people may have similar questions in mind. Please excuse me if I address things you already know. And please continue to engage if I miss your point.)
Looking back to your original post in this thread...I can't answer how much the 0.1.0 release differs from the version you downloaded. I'm not sure anyone can. This is how I understand it...The 0.1.0 release is the first tracked release. We now have a stable version in the master branch against which future updates can be compared. When you and I and others downloaded or cloned the repo before this release, we were getting a copy of the develop branch even as pull requests were being merged into it. So a clone in the morning could be different from a clone in the afternoon. With this release, the master has been tagged as v0.1.0 and set as the default. We can expect it to remain the same until the next release. Between now and then, work will continue in the develop branch. My decision to upgrade was based purely on my perception of stability. Previously the core developers didn't think their code was ready for public release, now they do. Your concerns may be different.
Greg, if you choose to reinstall/upgrade the authoring tool, you do not need to delete or uninstall anything in advance. The script will overwrite anything it needs to in the local adapt_authoring folder. It will delete and reinstall the adapt_framework using the most current release. And the versions of plug-ins that are downloaded will be those required by the newly installed adapt_framework.
The authoring tool's install script is used both to install and to upgrade. There is no separate upgrade command for the authoring tool. You simply rerun the install script. (So instead of the word "upgrade," I'm going to use the word "reinstall" throughout the rest of this post.) If you answer certain configuration questions one way, your data will be overwritten; if answer them another way, your data is preserved. More about that later. Installing the authoring tool installs that adapt framework. The install script checks to see if the framework is present, deletes it if it's present, then installs it. If you use the authoring tool's install script (for initial install or for reinstalling), you will get the latest release of the framework. The framework has been at v1.1.0 since May 2014. This is the version that the authoring tool has been installing. So at this point in development history, I can't imagine a typical installation that would need to have the framework upgraded to bring it up to v1.1.0. There may be installations that were completed in an atypical fashion, and I'm learning every day...but I don't have the knowledge to address them.
Back to reinstalling the authoring tool... I think the fundamental question to ask before reinstalling is whether you have data that needs to be preserved. The answer will not prevent you from reinstalling, but it will determine how you reinstall--or more precisely, how you answer certain configuration questions during your reinstall. If you answer the configuration questions about the master tenant with the same responses as the last time you installed, you will overwrite the master tenant in MongoDB, thereby losing all the data associated with: usernames, passwords, and course data. In other words, if during your last installation you answered questions about the master tenant using the defaults provided, and you use the defaults again during the reinstall, you will overwrite and lose your data. By responding with the same inputs, you will cause the master tenant to be recreated, and this means the data associated with it will be overwritten. If you want to preserve data when you reinstall, you can create a different master tenant which will leave the users and course data intact. In other words, if you accepted the defaults for the master tenant last time, you cannot do so this time. You'll need to be prepared to enter different data for the question
Set a unique name for your master tenant
Probably makes sense to be ready, too, to put something different in
Set the display name for your tenant
I personally haven't explored Mongo. I imagine there are other ways to save your data, reinstall the authoring tool, then reassociate it with the master tenant by directly manipulating MongoDB. Someone else will need to speak to that.
The adapt-cli is independent of and a prerequisite for both the framework and the authoring tool. You're going to need to monitor its evolution on your own and choose to upgrade it from time to time. Same with grunt and npm (and node some time in the future).
The plug-ins in the authoring tool can also be upgraded, but you'll want to do so using the Plugin Manager.
(I'm writing as a community member, not as a core developer. If anything I wrote here is incorrect or misleading, I hope someone will jump in and provide clarification.)