Improve room mapping FK diagnostics and cleanup

[SaltProphet]

Motivation

• Users creating rooms saw opaque foreign-key failures (rooms_user_id_fkey) after Daily.co room creation, leaving orphaned Daily rooms and insufficient diagnostic info to debug the database issue.
• The change aims to surface actionable SQL diagnostics and avoid leaving Daily.co rooms when local persistence fails.

Description

• Add a service-role preflight check using createServerSupabaseServiceClient() and auth.admin.getUserById to verify the session user exists in auth.users before attempting DB writes in createStaticRoom.
• Introduce formatSupabaseError to include message, code, details, and hint in returned DB error strings so FK failures are actionable.
• Add deleteDailyRoom that issues a DELETE to Daily.co to clean up a just-created room when the DB insert fails, and invoke it on insert error.
• Update unit tests in src/app/actions/createStaticRoom.test.ts to mock the service client and add a test verifying SQL diagnostics are included and the Daily.co cleanup DELETE is called on failure.

Testing

• Ran the unit tests with npm test -- src/app/actions/createStaticRoom.test.ts.
• All tests in that file passed: 6 passed, 6 total.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
secpriva	Ready	Preview, Comment	Mar 5, 2026 3:59pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 612f3643f3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Distinguish admin lookup failures from missing auth users

This branch treats any auth.admin.getUserById error the same as a confirmed missing user, so transient Auth API failures (or a temporary service-role misconfiguration) will reject room creation for valid logged-in users with the misleading message that the account does not exist. Because this check now runs before all writes, a control-plane hiccup can block the entire flow even when the session and DB insert path would otherwise work; only the !authUser?.user case should trigger the “missing account” response.

Useful? React with 👍 / 👎.