@LockOnGuy Saying "keep deleting" omits the fact that the key was last edited in 2018: https://osm.mapki.com/history/node/2488229258 . I'd suggest just adding name:ar back.
@%DA%95%D8%A7%D8%B3%D8%AA%DB%8C has been told at osm.org/user_blocks/6298 that they shouldn't change name:ar values incorrectly, and I'm sure you'll let us know if they do.

> blablablah, OSM uses uk route classifications,

Actually, no it doesn't. Various communities around the world have decided how best to map their road classifications into OSM ones, and it doesn't always match what is normal in the UK, because road classifications differ internationally. A German trunk road in OSM has certain characteristics that won't necessarily apply to a UK one, for example, and the same is true of a US motorway.
If the community in Russia says "the classification of this road is X" and you think it's Y, then they're right and you're wrong.

On which object?

Towton not Tophill

Nun Monkton not Notton

Perhaps Langthwaite not Langthorne?

The name on this one make sense - maybe this might help explain the limits of the "off by one" (or whatever it was) error?

Likely Grimston not Great Smeaton

Westerdale not West Witton

I've found https://www.yorkshirewater.com/media/sxnfahsl/market-information-publication.xlsx and that lists this as Kelfield, not Keld.
Maybe check the other Yorkshire ones at https://overpass-turbo.eu/s/1lut ?

I suspect they've cocked up the production of whatever data you used.
https://www.yorkshirewater.com/environment/bioresources/ has no obvious useful info on it; what did you use?

Long Marston not Lofthouse

Ryther not Ruston Parva

Kelfield not Keld

Wistow not Whitley

Likely Nunburnholme not Nun Monkton

Likely Crambe not Crakehall

Aldwark, not Aldfield STW, surely?

Flaxton not Flawith, surely?

ok, when did you survey it then?