Proposal: Integrate PR Auto-Reviewer to add structure and triage visibility

**Is your feature request related to a problem? Please describe.**
I noticed that while the project has a solid validation pipeline, there isn't much automated structure for incoming Pull Requests. Without standardized commit titles or size labels, it can be easy for PRs to slip through the cracks or sit in Draft status for months.

**Describe the solution you'd like**
I built an open-source, n8n-based PR Auto-Reviewer that I believe would be a great lightweight addition to your workflow.
It automatically:

- Checks PR titles against Conventional Commits formatting to keep the history clean.

- Adds size labels (Small/Medium/Large) so you know what can be reviewed quickly.

- Pushes a structured summary to Discord, which helps maintainers keep an eye on queue activity without constantly checking GitHub.

- Workflow repo & architecture: [https://github.com/yashgoyal5571/pr-auto-reviewer](https://github.com/yashgoyal5571/pr-auto-reviewer)

- Live Demo: [https://github.com/yashgoyal5571/pr-reviewer-test/pulls](https://github.com/yashgoyal5571/pr-reviewer-test/pulls)

**Additional context**
I am happy to submit a PR with just the workflow configuration if you’d like to test this out to help organize the queue!

未識別出任何儲存庫檔案、測試或進入點。先檢視現有的驗證管線和 PR 工作流程，然後釐清是否需要 n8n 整合、Conventional Commits 檢查、大小標籤和 Discord 摘要。完成應表示已有一套達成共識且經過測試的工作流程設定，維護者可以採用該設定。

由索引模型根據 Issue 內容生成。