Sorry if you feel you were misled Brad.
We did write a blog post detailing the level of integration with Divi not very long ago as well as updating the documentation page I linked to above.
https://toolset.com/2020/01/how-to-build-advanced-sites-with-toolset-and-divi/
You'll note in the comments some Divi users describing their set up as they continue to use Toolset and Divi together, while another user gave a reasonably lengthy description of that in our latest post about the recent Blocks update: https://toolset.com/2020/05/toolset-blocks-1-2-is-live/#comment-520389
I also note that with the current versions of Divi and Blocks, you can create content in Divi (in Divi Layouts) and then insert that Divi content using a Divi block, so right now you can create a template with Toolset and design some of it with Toolset blocks while also inserting content designed in Divi through its own block.
We're not recommending that, though, because it works today but who knows if it will work in a year's time.
Trying to keep up with the ever-evolving Divi—and Elementor, and Avada, and Visual Composer, and Oxygen, and today I have two tickets about Brizzy, whatever that is—is a huge drain on our resources that means we cannot improve our own products.
The introduction of the block editor means we can now focus on that, improving our product.
Toolset will work more-or-less well with future versions of these page builders—I expect some convergence around the block editing experience as with the recent Divi block that hopefully leads to more—but we won't persist with formal integrations that we are on the hook to maintain when the 3rd-parties make breaking changes.
That's the background to the current position.
If you'd like to apply for a refund, you can do that here: https://toolset.com/buy/refund/
