I assume that good practices is covering mapping of temporary feature as permament (Just i.e. if you map sand dune over the roads in some Dubai Desert https://i.dailymail.co.uk/i/pix/2017/02/23/08/3D51F73800000578-4232000-Dubai_highways_swallowed_by_sand-a-4_1487840356782.jpg), but conditional restrictions is specificly made for the reason, and should not work in offline data. Anyway it is great that you mentioned it.

We will add Notes to conditional restrictions in future.
I'll talk about proposing of solution on invisible conditional restrictions.

Thank you for proposing all of this.

Wishes of local communities is important for us not less than OSM rules.
We will change our approach to conditional restrictions and will add Notes on the map in places where conditional restrictions located in our future edits.
And, if we add Note, what it should contain? My guess is that "motor_vehicle:conditional=no @ (...)" enough to indicate that thing.
Do you think so? Maybe you have any info about where does this question was discussed?

Hi!
I apologize for the delayed answer,
We map road closures according to osm.wiki/Conditional_restrictions OSM wiki guide.
OSM data is not only for rendering, and big part of it not displaying in standard layer. Making this information visible (i.e. adding highway=construction) is actually "Tagging for the renederer" (osm.wiki/Tagging_for_the_renderer) and not preferred by community.
Please consider to adopt this schema of tagging for mapping conditional restrictions. Usage of conditional restrictions requires less maintenance in terms of monitoring and reverting expired edits. Conditional restrictions will stop affect routing right after expiration.
I will fix back your revert.
Thank you for reaching out, please tell me if you have any additions.

Hello, Jez. We are using third party dataset for address validation.

Esri Clarity dated by 30.09.2011
Use Esri or Bing to see "to" road.