docs(code-review): note that bot authors occupy billed seats

code-review/billing.mdx

@@ -7,6 +7,16 @@ Each developer with Code Review enabled counts as one seat. Seats can be assigne
 
 Code Review is billed as a monthly subscription. At the end of each billing period, your organization is charged for the number of seats that were active during that period.
 
+<Note>
+  Bots count as seats too. If a bot like Devin (`devin-ai-integration[bot]`) or
+  Claude (`claude[bot]`) opens a pull request that gets reviewed, it occupies a
+  seat like any other developer — including through
+  [auto-assignment](/code-review/people#auto-assign-seats-on-pr). To avoid
+  paying for bot seats, exclude bots with
+  [`exclude.authors`](/code-review/config#exclude-scans) or the org-wide author
+  filter, or remove their seats from **People**.
+</Note>
+
 <Info>
   If a developer no longer needs Code Review, remove their seat from **People**.
 

code-review/people.mdx

@@ -23,6 +23,16 @@ When auto-assignment is enabled:
 
 <Info>This can be turned off in **People** > **Auto-assign on PR**.</Info>
 
+<Note>
+  Bots count as developers too. If a bot like Devin
+  (`devin-ai-integration[bot]`) or Claude (`claude[bot]`) opens a pull request
+  while auto-assignment is on, it gets a seat and is billed like anyone else. To
+  keep bots out of review and billing, add their usernames to
+  [`exclude.authors`](/code-review/config#exclude-scans) or the org-wide author
+  filter — excluded authors are skipped before a seat is assigned. You can also
+  remove a bot's seat from **People** at any time.
+</Note>
+
 When seats are assigned automatically, the user whom the seat is assigned to will initially have an **Unassigned** role.
 You can change the role to Viewer, Member, Admin, or Owner.