chore: standardize CODEOWNERS on @petry-projects/org-leads team

[don-petry]

Summary

• Replace individual user/bot listings in .github/CODEOWNERS with the new @petry-projects/org-leads team
• Add standards/codeowners-standard.md documenting the policy

Why

• Stable CODEOWNERS files — owner changes become team membership changes, not multi-repo PRs
• Fixes GitHub App limitation — GitHub Apps cannot be code owners (platform limitation), but machine user @donpetry-bot in the team can satisfy require_code_owner_review. Closes pr-review-agent#27
• Centralized control — manage owners in one place

Team

@petry-projects/org-leads (newly created):

• @don-petry (maintainer)
• @donpetry-bot (member — machine user for pr-review-agent)

Test plan

• PR merges cleanly
• Org Leads team has push access to all org repos (already granted via API)
• Follow-up PRs migrate child repos (ContentTwin, TalkTerm, markets, broodly, google-app-scripts, bmad-bgreat-suite)
• Verify donpetry-bot approvals satisfy require_code_owner_review on TalkTerm after migration

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 39 minutes and 21 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2a445e7f-1a65-45e5-9f57-a6f4a0638a8f

📥 Commits

Reviewing files that changed from the base of the PR and between b51e2ed and 2f12201.

📒 Files selected for processing (2)

• .github/CODEOWNERS
• standards/codeowners-standard.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/standardize-codeowners-org-leads

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 39 minutes and 21 seconds.}

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Standardizes this repository’s CODEOWNERS configuration around the new @petry-projects/org-leads team and adds a written policy describing the intended org-wide CODEOWNERS approach.

Changes:

• Replace the default .github/CODEOWNERS owner list with @petry-projects/org-leads.
• Add standards/codeowners-standard.md defining the new CODEOWNERS policy and migration guidance.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
standards/codeowners-standard.md	Adds documentation for the new CODEOWNERS policy centered on @petry-projects/org-leads.
.github/CODEOWNERS	Switches the default owner rule to the @petry-projects/org-leads team and adds explanatory comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.