Propagating the dependencies of a module using "injected_interfaces" does not work properly

[ghost]

Description

public interface LivingEntityExt {
    void test();
}

Let's assume there is a mod named foo that injects the above interface into LivingEntity using injected_interfaces. Additionally, suppose there is a project named bar, which is structured as follows:

bar
─ bar-core
─ bar-impl

bar-core depends on foo as a modApi(...). In this case, bar-core can successfully call the test() method on the LivingEntity instance.

bar-impl depends on bar-core as a api(project(":bar-core", "namedElements")), meaning that the dependency on foo has been propagated. However, in this scenario, bar-impl cannot call the test() method on the LivingEntity instance, although it can access LivingEntityExt.

The fabric-api, which uses the same injected_interfaces, can use the injected methods without any issues even when dependencies are propagated. However, my project does not behave this way. What could be the problem?

I have tried various known methods such as cache invalidation, genSources, the fabric.loom.multiProjectOptimisation option, and others, but none have been effective.

My repository: https://github.com/GongjoongD0duk/batoru