imgui: Context recovery / graceful handling of bad state

I’m using vanilla Dear Imgui v1.60 WIP.

I have an app that exposes imgui API to plugins using a scripting language. Now, in my own code I can be sure that I am “well-behaved” - for example, I match calls to ImGui::Begin() with calls to ImGui::End(). But I can’t be sure that plugins will be the same. I also have live reloading of plugin scripts, and sometimes I end up trying to load plugin code that won’t compile (I can keep using the last-known-good version in this case) or worse: plugin code that isn’t well-behaved with respect to imgui API. Consider a plugin that consists entirely of [the scrip equivalent of] the following:

ImGui::Begin("This won't end well.");

I end up hitting this assertion:

IM_ASSERT(g.CurrentWindowStack.Size == 1);    // Mismatched Begin()/End() calls

As a feature request, is it possible to consider supporting more graceful failures? I don’t have a solid idea in mind, but you can see my use case above. It could be something like D3D12’s command lists, where the CloseCommandList() function returns a status code indicating whether this was a valid or malformed command list - maybe ImGui::EndFrame() could return a similar value and just drop the frame altogether, or render as much of it as it can [and I realize how this is a fuzzy concept - I’m just thinking out loud here].

Is there some other way to do this that I’m missing? I wouldn’t mind running the plugin code in its own imgui context (multiple context support rocks!), but currently that doesn’t seem to solve the problem I have.