chore: close TOC Project Reviews Subproject

[angellk]

Summary

This PR closes the TOC Project Reviews Subproject and removes it from active CNCF TOC documentation, labels, generated metadata, and issue/workflow routing.

The subproject served its purpose as a bridge during the TOC/TAG restructure. It helped preserve review practice, templates, and coordination while the restructured TAG model settled. That bridge is no longer needed as a standing TOC SubProject.

Going forward, governance and technical review work should route through the normal TOC operating model: the TOC retains responsibility for due diligence practice, criteria interpretation, delegation, and maturity decisions; TAG Chairs, Tech Leads, and delegated reviewers provide domain expertise and review capacity when requested by the TOC.

Changes

• Removes the Project Reviews SubProject from the root README and tags.yaml.
• Deletes the Project Reviews SubProject charter.
• Leaves the generated subproject README file untouched; the subproject listing is removed through tags.yaml per repository automation guidance.
• Moves reusable review templates and guidance from toc_subprojects/project-reviews-subproject/ to operations/project-reviews/.
• Updates moving-level and DD templates to point to the new operations location for:
  • General Technical Review questions
  • Domain Technical Review template
  • Governance Review template
• Removes sub/project-reviews from issue templates, generated review workflows, label definitions, and label routing.
• Updates TAG governance/charter language so TAG participation is framed as project governance and technical review support, Contributor Strategy, and other TOC-requested project support activities.

Rationale

The TOC Project Reviews Subproject was created to bridge a transition period. It provided a coordination point for project review work while the TOC/TAG structure was being updated.

The restructured model already expects TAG Chairs and Tech Leads to participate in governance and technical reviews. Keeping a separate Project Reviews SubProject now creates duplicate routing and unclear ownership. Closing the subproject clarifies that:

• the TOC owns the review process and maturity decisions;
• TAG Chairs, Tech Leads, and delegated reviewers support reviews under TOC purview;
• project review templates remain available as TOC operational materials;
• projects can still request governance and technical reviews through the existing issue templates.

Notes

This PR does not remove governance reviews, technical reviews, General Technical Review questions, Domain Technical Review templates, or Governance Review templates. It only closes the standing subproject and moves retained materials into TOC operations.

This update also addresses the repository automation comment: generated TAG/TOC subproject README files should not be directly edited or deleted. The generated subproject README is left unchanged in this PR; the active subproject registration is removed through tags.yaml.

Validation

• Ran git diff --check.
• Parsed updated YAML files:
  • .github/labels.yaml
  • tags.yaml
  • .github/ISSUE_TEMPLATE/gov-review.yml
  • .github/ISSUE_TEMPLATE/tech-review.yml
• Searched for remaining active-document references to the closed subproject label/path/name outside historical project artifacts.

[cncf-automation-bot]

This PR has been superseded by PR #2296 and has been automatically closed.