Okay. Follow up.
It actually looks like I didn’t break anything due to tossing around sudo root updates as previously speculated. Rather, this entire thing was caused by one simple thing it would seem.
WHAT HAPPENED TO ME:
After seeing a few mentions here and there about migrating to python3, I saw a few posts… somewhere?.. on here that mentioned it was performed with:
bench migrate-env **python_3.5/6_** <<<WRONG
Instead of:
bench migrate-env python3 <<<CORRECT
If you run that, with either “python3.6” or “python3.5”, it prepares for the update by backing up/archiving the python2.7 env (which I never quite figured out how to restore, but that’s probably just a noob mistake), then discovers that the folder, etc. doesn’t exist and errors out resulting in there not being any env mounted/present/whatever. So, if you go and look, and find the correct migrate command, it doesn’t work now and you end up screaming at your screen the 4hrs. Or more. But let’s go with 4 hrs.
So anyway. Yeah. Follow the latest and largest migrate threads (currently… this one?).