Not a bug - the fail-on-empty is a different meaning altogether (it applies when we know what the run is but there are no files selected for it). We don’t want to overload this to mean “this dependency is optional”.
This is related to this topic:
I think optional here is what we want. This applies to the required resource itself, not what gets selected from it.