That's precisely the expectation and indeed the whole purpose of type=street relations: to keep such tags in one place and remove clutter from technical bits of a single entity. Having a long list of previous names, etymologies and other "interesting" stuff at every single bit of a 200-part street is just insane. It's difficult to maintain, makes editing more complicated and doesn't bring any real benefits.

I would put it this way: all the data that is *really* used by consumers and changes the way the map is rendered (or the way searching works) should stay as ways' tags. Names are vital, in all the languages; old names, if they are still used by the populace or if they are still present on some other maps (like the shitty Google), should also stay in order to make searching by them possible. Old names from Russian Empire or early Soviet times are all in all just a piece of interesting information, so it's better not to clutter each segment with them.
Wikidata, etymology & similar tags... Well, they are indeed used by some consumers (like Organic Maps), but in the end they also only serve to provide some interesting information, nothing more. A good consumer which strives to provide such information to a user should parse street relations. In this case, IMHO, a one-to-one correspondence between a wikidata entity and an OSM entity takes precedence, so only the relation should keep such tags.

Then open an issue with MapComplete to recognize the tags from the relations, both from type=street and type=associatedStreet

partially reverted - it's a cow path at most, not a road

changeset/184703282

Once again, these are not parking_aisles

way/229528287 — this is not a parking_aisle. It's a road leading to a parking space, that is a regular service road. Please fix that

partly reverted - same comment as here: changeset/184454292

changeset/184702222

You've created two roads that lead inside the territory of a factory without setting any access tags, and these roads cross fences without any gates or something. That's incorrect, please fix that. If you do not know for sure what are the potential barriers to enter the territory, do not create such roads.

Because it's the purpose of that relation, with type=street, to unite all the tags that concern the whole of the street, like wikipedia, etymology, old_name (if not in use any more) and so on. So a software that shows etymologies of street names should get them from that relation as well.

убрал oneway

partly rv - once again, read what a parking_aisle is

changeset/184586453

way/1532167829 and way/971279000 are not parking_aisles. They lead from some other road to a parking lot; so they are just service roads. Only roads separating multiple parking spaces within a large parking lot should be mapped as service=parking_aisle , please read the linked documentation

Huh, well, now people have beaten a different path, with a "ladder" out of a tyre:
node/13963443403

operator:type=school ?

Definitely not residential; and please do not remove tracktype & surface unless you are sure that the surface has changed.
Fixed: changeset/184541702

😭

Well, I didn't notice anything extraordinary at that point. Definitely safe for hiking. I don't remember exactly, maybe there are some obstacles for vehicles... But closer to the top the road has definitely been severly damaged by streams, which created gullies right in the middle of it; so the upper part of the road is likeky smoothness=very_horrible by now. But I'm not sure, I only have some experience with driving on very_bad roads...

partly reverted - nope, no road there

changeset/184492748

reverted for those streets that are already present in relations (e. g. relation/20702822 , relation/18365886 , relation/15056525 etc.)

changeset/184468652

reverted for Giorgi Atoneli Street: already present at relation/18995349

changeset/184462925

You've connected a road way/1531511322 to a stream way/1099642911