Resend parity: POST /domains/claim. Adding a domain whose name is
already verified under a different team (moving it between two of
your own teams, or taking over one a previous integration added)
previously had no path at all other than a raw Prisma unique-
constraint error from createDomain.
Adds a DomainClaim model (name is globally unique on Domain, so a
second row for the same name can't exist until ownership actually
transfers) plus claimDomain/verifyDomainClaim in domain-service.ts.
Claiming issues a one-time TXT record and never re-touches the email
provider: the existing Domain row already has working DKIM/SPF/MX, so
once the requester proves DNS control, ownership transfers via one
db.$transaction (claim -> VERIFIED, domain.teamId -> requester) with
zero re-verification wait. The hourly domain-verification job now
also polls pending claims the same way it polls pending domains.
Verified against a real local Postgres: migration applies cleanly,
the unique index genuinely rejects a duplicate pending claim, and a
direct (non-mocked) claim+transfer round trip persists correctly on
re-read. 28/28 domain-service unit tests, 7/7 new + existing resend
domains API tests, 4/4 verification-job tests, full apps/web
`tsc --noEmit` and eslint clean.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>