Consuming highway=path, Take 3

What’s the goal here again? Warning data consumers that the range of what can be mapped as a highway=path in OSM is extremely wide (and that therefore they need to consider tags like surface and sac_scale for routing), or giving examples to mappers of paths that the community agrees should be tagged as highway=path? Because these are two very different goals.

I thought the goal was the former, and if so then the shared-use path (first picture in this post) is fine, but like I said somewhere else, the whole collage should be accompanied by a warning that not everyone would tag all of these examples as paths.