CODEOWNERS and a Review Checklist

Write a CODEOWNERS file and a pull request checklist for this repo. Ownership should match who can actually review, not an org chart fantasy. REPO Areas and the people who review them: [PATH → OWNERS] Anything that needs two reviews: [AUTH, BILLING, MIGRATIONS] Bot accounts that should not count: [BOTS] Default owner if a file matches nothing: [TEAM OR "I want unowned files to be visible"] DELIVER 1) The CODEOWNERS contents, most specific paths last (explain the precedence). A comment on the two-review paths and how branch protection enforces the count, because the file alone does not. 2) A short PR checklist: tests, migrations, env vars, feature flag, screenshots if UI, security note if auth or data access changed. 3) The line that says a drive-by refactor does not ride along with a bug fix. Keep it to one sentence so people read it. 4) How we notice an unowned path: a CI warning or a periodic check. Describe it. 5) What not to put in CODEOWNERS: a person who has left, a team with no members. Use GitHub's syntax. Do not invent usernames; use the handles I gave you and [HANDLE] placeholders otherwise.