yep, I forgot to split it, sorry about that

yes I can see it, there is for sure duplication in this case. But names are special, this is also specifically called out in the wiki, name is the exception
osm.wiki/Relation
> Tags describing the collection as a whole should go only on the relation (e.g. wikidata=*, destination=*, ...), except for the name, if any, which should go in the relation members, too.

yes, well aware, did you check this changeset?
Both of them are valid according to the wiki which is our reference
osm.wiki/Relation:waterway

> The relation should obviously be tagged with name=*, as well as name:*=* for names in other languages. However, because not every renderer supports waterway relations, each waterway should also be tagged with the local name=*. Short segments may have different names (e.g. a section of rapids) or no name (if it passes through a lake), and these can be tagged accordingly. Also, the local name of the waterway may change as it passes through different countries or regions that speak different languages, in this case tagging each way with the local name becomes more important, and the relation should have an appropriate mutlilingual name.

you are right; thanks; fixed with
osm.org/changeset/82218104

good catch, it was supposed to go to a node :-) merci