docs(codeowners): tighten comment to match org standard format

[don-petry]

Summary

The weekly compliance audit (issue #155) flagged codeowners-org-leads-not-first with 404 responses for all three CODEOWNERS lookup paths, indicating the file was missing when the audit ran. PR #153 had already merged the correct CODEOWNERS on 2026-05-04, so the repo is already compliant.

This PR:

• Updates the CODEOWNERS header comment to be more concise and align with the recommended style in the org standard (petry-projects/.github/standards/codeowners-standard.md)
• Makes explicit that @petry-projects/org-leads must be first on every owner line
• Keeps the single * @petry-projects/org-leads rule intact (already correct)

Closes #155

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 53 minutes and 36 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 32d55aeb-b2c2-4d68-a3e0-6a3d19e5794b

📥 Commits

Reviewing files that changed from the base of the PR and between b940c4e and ac09993.

📒 Files selected for processing (1)

• .github/CODEOWNERS

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-155-20260508-1411

---

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 and usage tips.}

[don-petry]

Self-review complete — no issues found. The change is comment-only; the compliance script strips comment lines before evaluating owner rules, so behavior is unchanged. The single * @petry-projects/org-leads rule remains correct.

CI checks are queued; nothing in this diff can cause a failure (no code, workflow, or dependency changes).

@petry-projects/org-leads — please review and merge when ready.

[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

Updates the repository’s .github/CODEOWNERS header comment to better match the organization’s CODEOWNERS standard and explicitly document the requirement that @petry-projects/org-leads appears first on every owner line.

Changes:

• Replaces the verbose CODEOWNERS header with a concise reference to the org standard doc.
• Adds an explicit rule statement requiring @petry-projects/org-leads to be first on every owner line.
• Adds a small clarifying comment above the default * rule (no functional ownership changes).

---

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

[donpetry-bot]

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: 1272435b13fdb4acb2de927d76806ee7e2280ff9
Review mode: triage-approved (single reviewer)

Summary

Prompt-only changes to the org status report template that reduce output size by ~29K bytes. Three changes: (1) Open Issues grouped by repo subsection instead of flat table, dropping the repeated Repo column; (2) duplicate [#N](url) | [title](url) cells merged into single [#N — title](url) cells across Needs Human Review, Open Issues, and Open Discussions tables; (3) MAX_BYTES bumped from 60000 to 64000 (still 1536 bytes below GitHub's 65536 char limit). No data-shape changes.

Linked issue analysis

No closing issue linked, but the PR body clearly describes the problem: daily report #233 exceeded the 60000-byte truncation threshold, causing head -c to drop the start of the report (the @org-leads opener and first three sections). The changes directly address this by shrinking the rendered output.

Findings

No issues found.

• MAX_BYTES 64000: Safe — leaves 1536 bytes of headroom below GitHub's 65536-char issue body limit. Combined with the ~29K reduction in report size, truncation should rarely trigger.
• Prompt template changes: Clean restructuring. The per-repo subsection format for Open Issues and the single-link cell pattern are consistent across all three tables.
• No security concerns: No secrets, auth, eval, injection vectors, or CI security changes.
• Copilot's suppressed comment about UTF-8 truncation in head -c is a pre-existing concern in the truncation step, not introduced by this PR.

CI status

All checks passed:

• Lint: ✓
• ShellCheck: ✓
• Agent Security Scan: ✓
• AgentShield: ✓
• CodeQL (actions): ✓
• SonarCloud: ✓ (0 new issues, 0 security hotspots)
• Dependency audit: ✓

---

Reviewed automatically by the PR-review agent (single-reviewer). Reply if you need a human review.