Organization creation form doesn't show an error when email is invalid

[stilla]

Summary

When creating a new organization, if the user enters an invalid/non-working email address, the form returns a 400 error silently — with no helpful feedback to the user about what went wrong.

Steps to reproduce

1. Start the organization creation flow
2. Enter an invalid or non-working email address
3. Submit the last step of the form

Expected behavior

The form should display a clear, inline error message indicating that a valid working email address is required.

Actual behavior

The form returns a HTTP 400 error with no user-facing explanation. The user has no way to know the email they entered is the problem.

Notes

A customer self-discovered the fix by trial and error. The fix is to surface proper validation feedback on the email field during organization creation.

_{Sent by @frankie567 from Create GitHub issue.}

[pieterbeulque]

@stilla-bot Can you capture these errors in ProductDetailsStep.tsx and surface them properly?

[stilla]

Good context. The pattern already exists — OrganizationSelectionPage.tsx uses setValidationErrors for exactly this. The issue in ProductDetailsStep.tsx is that the error handler just calls showApiResponse(400, ...) instead of surfacing validation detail, AND the form field is supportEmail while the API field is email, so we need custom mapping.

Here's the fix I'll implement:

_{💡 Reply with @stilla when you want me to jump in! Open in Stilla}

[stilla]

PR opened: polarsource/polar#10552

The fix:

• Extracts setError from the RHF form
• In submitOrg, checks if error.detail has a validation error for the email field
• Maps it to supportEmail (the form field name) so <FormMessage /> renders it inline
• Other errors still fall back to the generic showApiResponse