feat: add CODEOWNERS file

[dadodimauro]

Summary by CodeRabbit

• Chores
  • Updated repository configuration files.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A new .github/CODEOWNERS file was added to the repository that designates two code owners responsible for code governance and approval workflows.

Changes

Cohort / File(s)	Summary
Configuration .github/CODEOWNERS	Added new CODEOWNERS file specifying two designated code owners for repository-wide code ownership and review responsibility

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A carrot-munching tale so fine,
Two guardians now guard this line,
With CODEOWNERS set in place,
The repository finds its grace,
No hops left—the code's divine!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add CODEOWNERS file' accurately and clearly describes the main change: adding a new .github/CODEOWNERS file with two code owners.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codeowners

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 57e2dcf and ae1b803.

📒 Files selected for processing (1)

• .github/CODEOWNERS

🔇 Additional comments (1)

.github/CODEOWNERS (1)

1-2: LGTM!

The CODEOWNERS file is correctly formatted with both users designated as code owners for all repository files via the wildcard pattern.

---

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