feat: implement PR Sync automation

[v-Kaefer]

Linked Issue

• Closes Implement PR Sync automation and documentation #21

Milestone

• PR automation / repository hardening

Summary

• Implement the generic project_setup.pr_sync engine instead of leaving feat/pr-sync as documentation-only.
• Add the trusted .github/workflows/pr-sync.yml Action, chained after successful PR metadata validation / PR guardrails and handling draft/closed lifecycle events directly.
• Synchronize linked task label families, milestone, assignees, parent/sub-issue relationship, optional Project v2 membership, and PR lifecycle -> Project Status.
• Skip forks and promotion PRs (develop -> Q.A, Q.A -> main) before task-level mutations.
• Add committed prAutomation.sync defaults and distribute the workflow/module through the core installer.
• Add PR Sync unit/workflow-contract tests and make repository-quality validation require the new core files.
• Convert the EN/PT-BR PR Sync design documents into implementation contracts.
• Catch up documentation for recent CI hardening: metadata-only trusted promotion gates, .project-setup-source, and source-vs-embedded repository validation.
• Update the EN/PT-BR READMEs with PR Sync onboarding, Actions variables/secrets, security boundaries, and documentation links.
• Retarget this feature PR to develop, preserving the repository promotion flow feature -> develop -> Q.A -> main.

How to test

• Run make check from the repository root.
• Run python -m unittest tests.test_pr_sync -v to exercise PR Sync parsing, lifecycle mapping, metadata synchronization, idempotency, fork/promotion safety, and workflow contract.
• Confirm Repository quality CI is green after the PR is retargeted to develop.
• Exercise live Project v2 synchronization only in the dedicated Q.A sandbox before promotion to main.

Known risks

• Project v2 synchronization is optional and requires both PROJECT_SETUP_PAT and PROJECT_SETUP_PROJECT_NUMBER; repository-scoped PR/task synchronization continues when they are absent.
• Label synchronization is additive and intentionally does not delete stale PR labels.
• Reviewer selection is intentionally outside PR Sync and remains a PR Guardrails/review-policy responsibility.
• The current GPA validation workflow is named PR metadata validation; PR Sync also recognizes the reference-compatible PR guardrails name for the intended future Guardrails naming.

DoD checklist

• PR Sync engine implemented.
• Trusted GitHub Actions workflow implemented.
• Configuration and installer integration implemented.
• Unit and workflow-contract tests added.
• Repository-quality gate updated to require PR Sync core files.
• EN/PT-BR implementation documentation updated.
• EN/PT-BR README onboarding updated.
• Recent CI/source-mode hardening documentation caught up.
• PR target corrected to develop.
• Hosted Repository quality CI green on the final PR head (31409108190).

[coderabbitai]

Warning

Review limit reached

@v-Kaefer, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d70dba4c-2649-4873-aa69-3fe5c14afc0e

📥 Commits

Reviewing files that changed from the base of the PR and between e403d3a and 8ea1970.

📒 Files selected for processing (14)

• .github/workflows/pr-sync.yml
• README.md
• README.pt-BR.md
• docs/DOCUMENTATION-GUIDE.md
• docs/repo/branching-policy.md
• docs/repo/branching-policy.pt-BR.md
• docs/repo/pr-sync.md
• docs/repo/pr-sync.pt-BR.md
• docs/repo/project-setup-shared-tool.md
• project_setup.json
• project_setup/installer.py
• project_setup/pr_sync.py
• scripts/validation/repo_quality.py
• tests/test_pr_sync.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}