seems like my fix for finding the right classes by iterating over every known mapping namespace broke. Yarn mappings don't get shipped with the fabric loader anymore. - or did it really ever work? At this point I'm pretty confused.
And the tricky part is, this only shows when trying the mod in a real client, since the run task of gradle does run the client in yarn mappings (thanks for the tool to test the mod in a real szenario -.-).

Anyway. The only mapping consistently mapping to the right runtime mapping would be intermediary. Since the fabric loader will map minecraft to intermediary in a real client this would render "un"-mapping outside of testing in the ide pretty useless.
Moreover, I would argue it makes the whole thing of having the class in the config pretty useless.
While the classes in yarn mapping themselves are highly technical, at least they are intuitively understandable.
However, nobody will understand net.minecraft.class_1794 being a hoe.

At this point I would suggest to just go for Ids with special handling for allowing #tags. This would be slightly less powerful by itself, but would be more vanilla like and even allow the user to group items together the way they want by creating a new tag via data pack.

What's your opinion on this matter?