Add a CODEOWNERS file

Add a CODEOWNERS file that maps our core packages to their owners. Make @sanaa the owner of the auth package, @marco the owner of the database package, and @frontend-team the owner of the UI folder. Place the file in the repository root so PRs touching those paths request reviews from the right people.

Before I add CODEOWNERS, make approvals less noisy and more reliable. Assign owners to precise paths so small docs edits don’t ping teams, prefer individual owners for fast response and a team alias for broad areas, and flag any path that currently lacks a clear owner. Note any owner who is on leave or overloaded so I can add a backup reviewer.

A refactor touched many paths and every owner got a review request, so reviews stalled. I’m worried about review fatigue and missed coverage. I don’t know whether to pare back CODEOWNERS to individual subpaths or add a rule to suppress notifications for mass renames. Should I change the file now or handle this PR case-by-case? What minimizes noise without reducing accountability?

We repeatedly get review storms where many owners are pinged for broad changes, and we also have gaps where nobody owns critical files. That slows merges and creates coverage blind spots. Which habit should I change first — more granular path rules, establishing backups for owners, or a policy to limit owner pings on big renames? Recommend one actionable step and how to roll it out across the teams.