chore: expand CODEOWNERS coverage

[KooshaPari]

User description

Expands CODEOWNERS to cover code areas, configuration, and sensitive paths. Per wave-22 CODEOWNERS verify audit. API-only, canonical template (no named subteams).

---

Note

Low Risk
Low risk: adds CODEOWNERS metadata only, affecting review routing/required approvals but not runtime behavior.

Overview
Adds a new .github/CODEOWNERS file to broaden ownership coverage across key code (/src, /tests, /docs), configuration files, and sensitive paths (including workflows and SECURITY.md), with @KooshaPari as the default and explicit owner.

^{Reviewed by Cursor Bugbot for commit 3577e78. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Expand code ownership coverage for core, config, and sensitive files

What Changed

• Added a CODEOWNERS file so key areas now have an assigned reviewer
• Covers source code, tests, docs, configuration files, workflows, and security files
• Uses the same owner across all covered paths, including the default fallback

Impact

✅ Clearer review routing
✅ Fewer unowned file changes
✅ Faster approval for sensitive updates

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 33 minutes and 53 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 33 minutes and 53 seconds.

⌛ 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: e9cecba8-38d6-41d7-9176-77d9f332bd93

📥 Commits

Reviewing files that changed from the base of the PR and between 445b556 and 3577e78.

📒 Files selected for processing (1)

• .github/CODEOWNERS

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/codeowners-expand-2026-04-27

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/codeowners-expand-2026-04-27

---

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.}

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 3577e78. Configure here.}

[cursor]

CODEOWNERS references nonexistent paths in repo

Medium Severity

The new ownership rules target /src/, /package.json, and /go.mod, but this repository is a Rust workspace whose sources live under /crates/ and /bin/ and contains neither a package.json nor a go.mod. These patterns match no files, so the "expanded coverage" intent is not actually achieved for the code areas — those files fall through to the wildcard owner. GitHub will also surface unknown-path warnings on the CODEOWNERS settings page.

 

^{Reviewed by Cursor Bugbot for commit 3577e78. Configure here.}

[cursor]

Duplicate CODEOWNERS files; root file becomes dead

Low Severity

A CODEOWNERS file already exists at the repository root. GitHub picks only one CODEOWNERS file using the precedence .github/ > root > docs/, so introducing .github/CODEOWNERS silently shadows the existing root file. The root copy becomes dead configuration that future maintainers may edit without effect, leading to confusion and drift between the two files.

 

^{Reviewed by Cursor Bugbot for commit 3577e78. Configure here.}