OK, my notes - there's a lot... Pull up a chair.
OK First, There's no fundamental changes in structure in the cabinets in THIS BUILD... ...Yet - won't say I don't have experiments running and there may be a reason the storage got rearranged into 'stacks'
For those venturing into betaland...
YOU WILL Have a metric ton of orphaned scripts. (I think it was a half dozen or so)
Sorry - that's me. After everythign comes up green if you still have a bunch of 'this entity is no longer being provided by...' *dojotools(foo)... Yeahhh
Aligning things to fit my own ruleset points above but it serves something coming soon-ish? And predictability becomes very important very now. I'm doing it as 'efficiently' as I can causing as few possible naming conflicts as possible. There will be payoffs besides a taxonomy.
There ARE new tools - visit through your scripts and see who is-isn't exposed. There may be a reason I renamed the ones I did - Note how suddenly a half dozen Dojotools dropped off your exposed list? 
You're welcome. The functionality is still there. Had to make room for the newcomers.
"...But Nathan, I don't have..."
Yes, I know. Most of you won't have all, or maybe even HALF of the home lab stack I currently have in my head. That's perfectly fine. I'm COUNTING on it in fact. Test Subj... cough Annnnyway.
The tooling is SPECIFICALLY designed to fail safe, closed and explain itself when it can't reach a server. Conversely - that also means it can help you through the setup too. A lot of these new tools need a 'setup' routing to register the actual server [ TRANSPORT://URL:PORT ] etc. But that means we can also gate the tool on - is it even installed? If not, then an entire class of data falls out of the machine automagically. Yes, these all store in a central cabinet registry so tools can tell you who is registered where for what... (And maybe what permissions it needs...) No tokens will NOT be part of what your agent can register, ON PURPOSE. There are a few more you may want to add as dummies - I'll make sure the readme and install instructions get bumped.
Basically, If [TOOL X] isn't in your stack, and you don't configure "Dojotools (foo for Tool X)" it SHOULDNT break stuff - and if it does, I want to know, because that's a bug.
What's going on right now is I'm rapidly expanding the tool surface across the easiest to integrate, easiest to manage, easiest to maintain free docker container-based distros I could find for [Insert Tool Class HERE] so I could get a realistic base operating environment. The next few posts will describe what's about to happen with it.
Then by having 'Stacks' and 'Lenses' we have a noun-verb class set consistent across tool semantic category. that can either read or write structure shaped like [FOO] at will... I'm dividing this layer from the 'sutra' layer intentionally because that layer defines the 'adapter' surface for what a thing can offer.
(TL; DR, Nathan, WORDS...) FINE...
That ^^^ Basically, translates to... I want data about dolphins in the back office - but only in wiki pages, roomstate, or inventory. Get me back-office inventory dolphins and stories about them and the room...Cool?
(So you don't think I'm nuts - that particular formula would yield a max storage temperature for my wife's office stockroom and the temp sensor attached... Because the particular item labeled 'dolphin' could be temp sensitive... See? Inventory dolphins in the Back Office...)
For just about any external we decide if it's a read - contribute evidence type, (PaperlessNGX) 'Lens' and/ or a write storage class, like the Cabinet system, WikiJS or. Then pick the shape of what you're connecting to and go grab those scripts that look and act like your system, use them as a model to write your own adapters. You should have examples of every capability I could think of across addressable read and/or write types between all the plugins. If you come up with new patterns Heck yeah. Lenses should be small, laser focused and offer flexible call options the agent doesn't have to ask why they want it, should be obvious or don't write the lens. The best ones by far have been me polling one of the agents and asking what they need.
Combine this with LiveDrawer and a nested structure - ohhboy I'm almost as excited as a Dungeon AI with a new toe ring. I'll be looking at a few summary views of nested structures in one call if I can come up with a way to not absolutely explode context with the potential recursion 
I won't have Obsidian in x.7.0. I THINK I'm going to solve Obsidian as a DAV connector; it is more flexible than just vaults... - More coming soon, but if I suddenly go Fallout themed, you know what happened.
Project help is in the build - the tool isnt,still needs a LOT of work, 'Finance' Connects to Firefly, I have not round tripped the accounts list or transactions yet - thus it has not made the cut as v.1.0.0 yet. It will earn its wings (Safe manipulation of accounts) before release or get kicked back to next month. << There be dragons here.
Backup before you leap - CabStacks are new after, all - but they're fundamentally basically a dirty trick on top of the same medium so ... Let's see what happens.
They're awesome and No Dungeon Crawler or Zork IP was harmed in the beginnings of our test 'game' (Yes quests are coming... Go break that and report bugs, that helps something else planned that's NOT a game.)