Auth “Send SMS” Hook: /otp fails with missing auth.otp_attempts → verifyOtp “token expired or invalid”

# Bug report Environment - Supabase Cloud project: qqjrnulwsrbshdoncojz (production) - Auth: Phone OTP with “Send SMS” Hook enabled - Client: supabase-js 2.x (SSR + Browser, Next.js 15 App Router) - Edge Function: relay-auth (Deno edge) sends SMS via AWS SNS (hook-only) - Hook secret configured (Standard Webhooks header supported) Context - We switched to the new Auth “Send SMS” hook. The dashboard calls supabase.auth.signInWithOtp() directly. Supabase invokes our hook, and we deliver the SMS successfully via AWS SNS. However, OTP verification fails because Supabase’s / otp endpoint errors before storing the OTP. Problem - /otp returns 500 with “relation auth.otp_attempts does not exist” (SQLSTATE 42P01) - As a result, verifyOtp() responds “token has expired or is invalid” even though the user received a code. Steps To Reproduce 1. Enable Phone provider and configure Auth → Hooks → Send SMS to our edge function URL (relay-auth). 2. Client calls: - signInWithOtp({ phone, options: { shouldCreateUser: true, channel: 'sms' } }) 3. Hook runs and returns 200; SMS delivered (confirmed by logs). 4. Supabase logs show /otp 500 error (missing auth.otp_attempts). 5. Client calls verifyOtp({ phone, token, type: 'sms' }) → “token has expired or is invalid”. Relevant Logs - /otp failure - msg: Unhandled server error: ERROR: relation "otp_attempts" does not exist (SQLSTATE 42P01) - path: /otp - referer: http://localhost:3000 - /verify failure - msg: token has expired or is invalid - path: /verify (We can provide full log lines with request IDs if helpful.) Expected Behavior - /otp persists OTP attempt and returns 2xx. - verifyOtp succeeds when a valid code is provided. Actual Behavior - /otp 500 due to missing auth.otp_attempts, so no OTP is stored. - verifyOtp fails with “token expired or invalid”. What We Tried - Attempted to create the table via SQL Editor: - CREATE TABLE auth.…