Proposed resolution:

This wording is relative to N4928.

1. Modify [version.syn], header <version> synopsis, as indicated:

   […]
   #define __cpp_lib_ranges_stride                     202207L // also in <ranges>
   #define __cpp_lib_ranges_to_container               202202L // also in <ranges>
   #define __cpp_lib_ranges_zip                        202110L // also in <ranges>, <tuple>, <utility>
   […]
   

[ Issaquah 2023-02-08 Status changed: New → NAD. ]

No consensus to change anything. The macro name is just a unique identifier, it doesn't have to be a precise description of the feature.

LWG 3785 enables ranges::to to construct a non-range object from a range, confirming that this is the intended part of the original design.

However, the feature test macro for ranges::to is still named __cpp_lib_ranges_to_container, where the "container" part seems confusing to users.