Validate product website on pull requests before Pages deployment

[masarray]

Summary

• run the full GPL, commercial-license, provenance, terminology, generated-documentation, and static-site validation path on pull requests that affect the public website
• upload and deploy the Pages artifact only for pushes to main or manual dispatch
• separate validation from deployment so public-site defects are caught before merge
• use event/ref-scoped concurrency to avoid a pull-request validation cancelling a production deployment

Why

The licensing and wording migration changes public metadata, documentation generation, and the landing page. This workflow makes the same reviewed site build a required pre-merge signal and then deploys that validated output after merge.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.