docs(13-01): record PAX8 as first DB-toggle-gates-action precedent

Note in Operator config / Integration disable that the pax8 toggle is
the first integration where the DB toggle stops an action (scheduler
skip + 403 on manual sync route) rather than only suppressing
health-check display.

CLAUDE.md

@@ -137,6 +137,10 @@ Examples: `getAutotaskClient()`, `getMsgraphClient()`, `getDattoRmmClient()`,
     `disabled_at`, and an optional `disabled_reason`.
   In both cases live auth checks still run (logs surface the underlying
   state); the UI ignores the result for disabled integrations.
+  - **PAX8 is the first exception**: disabling `key='pax8'` doesn't just
+    suppress health-check display — the `pax8-daily` scheduler branch skips
+    `fullSync()` and `POST /api/pax8/sync` returns 403. Every other
+    integration's toggle today is display-only.
 
 ## Watch out for
 - A `.env` file is committed to the repo. Treat secrets as potentially real; don't