Reading that the "normal power mode" would require sending GPS coordinates to a central database explains the limited support/availability I guess. And the regulations are different per country..
Creating wifi 6E hotspots still seems to be impossible with windows and the available wifi6E hardware.
And sellers seem to take advantage of customers, who mostly don't understand the difference between wifi6 and wifi6E. Even Meta seems to do it for Quest3. They advertise a dedicated, super fast wifi TP-Link USB-stick which only supports wifi6 and not 6E(which is the whole point of using wifi6 with the Quest3)
Anyway..
Also, trying something new out will most likely have hiccups. Ultimately it may fail. But that doesn't mean it's not worth the effort.
The thing may rapidly evolve if it's being hard-tested on actual code and actual issues. For example it will be probably changed so that it will iterate until tests are actually running (and maybe some static checking can help it, like not deleting tests).
Waiting to see what happens. I expect it will find its niche in development and become actually useful, taking off menial tasks from developers.
However, every PR adds load and complexity to community projects.
As another commenter suggested, doing these kind of experiments on separate forks sound a bit less intrusive. Could be a take away from this experiment and set a good example.
There are many cool projects on GitHub that are just accumulating PRs for years, until the maintainer ultimately gives up and someone forks it and cherry-picks the working PRs. I've than that myself.
I'm super worried that we'll end up with more and more of these projects and abandoned forks :/