Ah. I'd much rather see explicit scope within the registrar, so that the procedural macro ends up in the module tree of the original library.
Your use of a macro construct right there is still impossible, FYI.