I'd like to enable AUH for the meta-riscv layer, so that we can automatically update custom recipes (e.g. linux-mainline.bb, which is a catch-all for multiple BSPs which build with differing SRC_URI lists and options). Additionally, it would be good to support supplemental maintainer lists so that if a project beyond OE-core wants to assign its own maintainers for recipes, they can run AUH and receive update notices. Is this something worth doing?
Worth noting that there are some edge cases to handle if this is of interest, too. For example, in meta-riscv we have linux-mainline.bb, which contains SRC_URI lists and various configs (via override) for multiple different BSPs. It also inherits from linux-yocto.inc indirectly, which has RECIPE_NO_UPDATE_REASON set, so it gets ignored by default by AUH. We could override that in the recipe, but it may also be worth adding some extra logic for such cases.