I guess technically the issue is that OneBit VFD didn't use the exact theme name for its cfg file and resources folder. Seems to make sense to enforce that for future themes .
Hmm, I suppose it is possible to ensure all theme contents are uniquely named (we already extract the file list from the theme zip files) but we'd want to exclude "shared" stuff -- fonts come to mind. Is there anything else that may be typically shared?
(Being able to see what fonts are shared across multiple themes might make it easier to identify fonts that could be pulled into the global font pack...)