Are you saying that I can just leave template_info.php & stylesheet.css in barebones where they're currently at and that by selecting the barebones template in the admin module, this is what tells zen to look in the barebones subdirectory within includes/templates?
And if the answer to that third option is a resounding YES, then here's my next question:
Is it accurate to say the following:
1. There's no reason to create an override a level beneath classic or move any barebones files in to includes/templates/classic because classic and barebones folders have the exact same file structure (housing the CSS & the PHP file for their respective templates) and by telling zen via the admin module that my preferred template is barebones, zen will never look in classic for those files and so there's no reason to override them - that in fact, the installation of the barebones template created the override system for that level of the directory structure?
2. That since the override rule for includes/templates/template_default is to create an override at the same level, any files within template_default that would need updating would be copied up to the already existing barebones folder on the same level, and so therefore, there is no reason to have to move any copies of any barebones files to the template_default folder?
3. If numbers 1 & 2 are true, then it must also be true that since I already have an override folder at the includes/template level, simply by virtue of having installed the barebones template and therefore, there's really nothing for me to do but move on to setting up the overrides for the includes/modules and includes/languages.