[codex] fix delete email OTP captcha

[riderx]

Summary (AI generated)

• Added Turnstile to the account-delete email OTP verification flow.
• Pass the captcha token into Supabase signInWithOtp and show captcha-specific send failures.
• Added a targeted typos exclude for an already-committed migration filename containing indexs, keeping the migration filename stable.
• Updated read_replicate/schema_replicate.sql for indexes introduced by the existing latest migration.

Motivation (AI generated)

The delete-account flow requires recent email OTP verification, but its OTP send path did not provide a captcha token. In production, Supabase captcha enforcement can reject the send request, leaving users stuck on a generic verification failure toast. The CI-only updates let the existing base migration pass typo and read-replica schema checks without renaming a committed migration.

Business Impact (AI generated)

This unblocks users who need to verify email ownership before deleting an account, including cases where they need to reuse an app ID from an old account. It should reduce support load while preserving captcha protection on the OTP send action.

Test Plan (AI generated)

• bun lint
• bun run typecheck:frontend
• bun run build
• bunx typos .
• MAIN_SUPABASE_DB_URL=postgresql://postgres:postgres@127.0.0.1:56082/postgres bun run readreplicate:check-schema
• Commit hook full typecheck: bun run cli:typecheck && bun run typecheck:backend && bun run typecheck:frontend

[coderabbitai]

Warning

Review limit reached

@riderx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 1 second. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ffaac542-2116-4be1-aefc-f8fc67568f57

📥 Commits

Reviewing files that changed from the base of the PR and between 00e3df3 and e947225.

📒 Files selected for processing (3)

• .typos.toml
• read_replicate/schema_replicate.sql
• src/pages/resend_email.vue

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing codex/fix-delete-email-otp-captcha (e947225) with main (00e3df3)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.