Esp. for the attention of chairs @Kangz @kdashg , team contact @tidoust , WebGPU editors @kainino0x @litherum @toji , and WGSL editors @dneto0 @alan-baker . If you deem it appropriate, I'd like to act and realize migration quickly and then implement Actions-based sync.

When this repository had the inception of tree-sitter grammar, the idea was to propose to host it next to other tree-sitter projects for better visibility. I intermittently updated a repository for reference purposes until we found a better home for the derivative source, npm, and crates packages.

Yesterday, @DJMcNab brought up the following suggestion in the attachment to the important contribution found in the PR itself (in #3772 (comment) comment):

... The only "official" documented way to acquire the grammar is to clone this repo and run generate-grammar.py, however that method is very inconvenient. It would be helpful if there were a "guarantee" of where to find it. A link in the spec to the aforementioned URL might be sufficient for that, although that seems slightly naïve. ...

This suggestion is a good initiative to act on the following clause of Community Group Charter (in https://gpuweb.github.io/admin/cg-charter.html URL):

... The Community Group may develop a continuous integration mechanism to validate the grammar of WebGPU Shading Language against syntactic ambiguities and potential mechanical issues with primary reliance on an open-source, commercially-permissive license tool that can report ambiguity and generate playgrounds that can run on the Web so that community can leverage and extend easily to enhance the ecosystem. Such software will be developed using the W3C Software and Document License. ...

Since this clause is analogous to CTS, I think we could use this organization for hosting and automatically syncing. I'd not like to point to a repository in my personal account as a reliable URL, and I think it'd significantly undermine community spirit.

Kind regards,
Thank you very much.