"use client"; /** * ScimCard (TASK-0132) — the org admin "Integrations → SCIM" surface. * * A SELF-CONTAINED component (like SsoTabs): it takes `orgId` and owns its * own data (react-query against `scimApi`). Mounted on the standalone * `/org/[orgId]/admin/integrations` route next to SsoTabs; TASK-0133 hosts * both inside the org console. * * Views: * - not enabled → an empty state + an "Enable SCIM" form (user email domain * for `@`-less usernames, default role, auto-join toggle). * - enabled → the connection summary (endpoint + curl example), the * REVEAL-ONCE bearer-token panel (shown exactly once after enable/rotate), * a test-connection panel (the browser pastes the token back — the server * never stores it), rotate, and the danger-zone disable. * * The bearer token is REVEAL-ONCE: it is generated server-side and returned * exactly once in the enable/rotate response (the server stores only its * SHA-256 hash). The read returns only `tokenHint` (the last 4 chars) — * there is no "reveal" after save. * * A11y: inputs are real labelled fields (Field renders a