Microsoft
Microsoft
Thank you for re-validating and confirming. Unfortunately, WinGet and the Microsoft Store even have no control over this as noted. The app developer or publisher are completely responsible for this and WinGet, via the Store, just provides what the developer or publisher most recently published to the Store, and this even includes built-in Windows apps. As for the version numbers, there is no standard; each app developer and publisher can define whatever they want, and this also goes for built-in Windows apps. I fully concur that both of these "nuances" add friction, but "it is what it is" is the only statement I can provide on this.
I have no idea why the third party site you called out above provided the necessary version as that's simply providing a link to what's in the Store similar to what WinGet does. Without seeing exactly what you downloaded previously I can only guess that you caught this app at some point when the publisher had published multiple versions of the overall package in succession and the time you ran WinGet, it did not include the desired version but the time you grabbed the URL from the third party it was included. Perhaps they found a bug and temporarily removed it from the package and reverted to an older version.
Ultimately though, this all outside of WinGet's control and for built-in Windows app issues, please file feedback in the Windows Feedback Hub or open a Windows support case. We can certainly try to communicate with built-in Windows app owners internally if we are aware (or made aware of) issues (and I suspect Roy may have actually done that based on this thread as we did chat about this) but that's generally not (rarely in fact) the best way to receive support for a customer for a variety of reasons.