Currently only BeanRegistrationCodeFragmentsCustomizer can be used to customize BeanRegistrationCodeFragments but for parent/child context support we'd like to be able to apply customization directly from a BeanRegistrationAotContribution.
Making such a change should also allow us to from the BeanRegistrationCodeFragmentsCustomizer entirely since the same functionality could be achieved using the existing BeanRegistrationAotProcessor interface.