OG_blueprint action on OG group deletion

Hi,

Finally upgraded to OG_blueprints. Awesome!

Just tried to delete an OG group.
Saw new choices inserted by blueprints.


Remove the associated bundle, but retain the bundle version history. Since you are deleting this node type, the only use case is if you intend to create a new group node type to replace this one, and you want the new group node type to inherit the bundle version history from the old group node type. (Note that the UI facilitating this has not yet been implemented.)

Purge all data on the associated bundle from the database. Purging means removing all trace of the bundle from the database (i.e., deleting the entire version history). Consequently, you should select this option ONLY if you have no further need for that data.

I found the reference to deleting "node type" confusing. I assumed that it refered to "content type" but I am not deleting a content type. I am deleting a unique node that is defined/patterned from a particular content type.

However, this is even more confusing. It says that "Since you are deleting this node type, the only use case is if you intend to create a new group node type to replace this one..." My usecase is that I want to make a new group node. not a new group node type.

I don't understand why deleting a group (rather than a group content type) should have anything at all to do with OG Blueprints. If I delete a group, I would expect that I could use the same blueprint to make another similar one if I chose. I believe this is how OG Collections worked.

Is it possible that this complex choice involved in preserving or deleting bundles or purging the database relates to the deletion of a group content "type" that OG Blueprints is intending to serve with specific bundle? If so, it seems that this delete warning and functionality should be shown if I delete a group content type rather than if I delete a unique group?

Am I making sense?
Am I misunderstanding something important in the function of OG Blueprints?
Is this a bug, a lack of clarity, or a feature I don't understand?

What do I have to do to correctly delete my OG group without affecting anything in OG_Blueprints (because I really do want to use the same bundle (and release) to create a new group?

Thanks