i totally understand/agree on that, but currently the implementation is, within the

hydrate_sources()

@rule

, taking the match result data and branching on the value of the

--glob-expansion-failure

global option (which becomes a

SingletonRule

) to warn or error or ignore match failures, and it's not clear to me where to perform that now