I feel like none of these solutions are mutually exclusive, necessarily. Like, for the default provided builds, you could have a checkbox in the menu to enable the functionality AND have an esoteric way to default it on AND have the ability to make custom builds that enable it. So then the regular Decker user has the ability to turn on the functionality but only by doing so intentionally, and then if someone wants to use these features in a more neatly packaged up type project, it's on them to ship a custom build and then for the end user it's no different as a potential threat vector to downloading any other random software online. I think this kind of mix could make things workable