Thank you GitHub for wrongly submitting the issue early
So, hopefully I can write quickly enough before anyone sees this incomplete issue.

Architectury API allows to register resource reload listeners via ReloadListenerRegistry. This is neat up until you see the Fabric/Quilt's take on the system.

In the Fabric and Quilt ecosystem those reloaders are named and have stable identifiers, this is important as it allows other reloaders to re-order them (depend or make sure to run before, etc).
This can be very important in the case of addon mods, and others.

This expectation is entirely wrecked with Architectury API not letting mods name their reloaders and giving them random IDs.
In addition, it doesn't let anyone re-order reloaders, which led to some people trying to order using registration call order (and that is entirely wrecked by Quilt's own reloader sorter since it's not using Lists but HashMaps).

It would be nice to add a way to give stable names and specify dependencies on resource reloaders inside of Architectury API to satisfy Fabric and Quilt's expectations.