chore: add CODEOWNERS

[getappz]

Summary

• Adds .github/CODEOWNERS with a single wildcard rule (* @getappz) — auto-requests review on every PR
• Checked collaborators first: gh api repos/getappz/agentflare/collaborators returns only @getappz, so this is a single-maintainer repo today. Deliberately not splitting into per-path rules (crates/ vs src/ vs site/ etc.) since a granular ownership map with one name behind every path is ceremony, not real protection — worth revisiting once there's more than one regular contributor.

Test plan

• Syntax matches GitHub's documented CODEOWNERS format (pattern + owner)

Summary by CodeRabbit

• Chores
  • Updated repository ownership configuration to establish a single, repository-wide maintenance rule.
  • Added guidance indicating the rule can be refined into path-scoped entries once additional contributors are added.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 8f1245d6-13b6-452b-921d-577b9d197365

📥 Commits

Reviewing files that changed from the base of the PR and between bef21f5 and 1138e82.

📒 Files selected for processing (1)

• .github/CODEOWNERS

📝 Walkthrough

Walkthrough

Adds a .github/CODEOWNERS file with a repository-wide ownership rule and comments describing the intended transition to per-directory ownership.

Changes

Ownership configuration

Layer / File(s)	Summary
Repository-wide ownership rule .github/CODEOWNERS	Adds a wildcard CODEOWNERS rule and comments explaining the current single-maintainer setup and future directory-specific rules.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly names the main change: adding a CODEOWNERS file.
Description check	✅ Passed	The summary and test plan are present, but the template's review notes and repo-standard test checklist are missing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/add-codeowners

---

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