I think then the only thing left to do is clarify in the docs that the final target generated by a tailor alias macro must be a drop-in replacement for the target it's replacing. That probably means that it can add fields and other targets, but taking them away seems to lead to duplicates like this