Signup Form

Requirements

• The supplied form has full name, email, password and confirmation fields. Start with empty values and no errors; use framework state and prevent navigation on submit.
• Validate trimmed name length of at least 2, a trimmed email with text before/after @ and a dotted domain, password length of at least 8, and a nonempty confirmation equal to the password. Show Enter at least 2 characters., Enter a valid email., Use at least 8 characters., and Passwords must match. for the corresponding invalid fields, with synchronized aria-invalid state.
• Invalid submissions send no request. After the first submission, editing fields revalidates errors and clears the submission message.
• For valid values POST JSON to /api/demo/signup with exactly name (trimmed), email (trimmed/lowercase), and password (unchanged). Confirmation remains client-side. Display Submitting… and disable fields and submit while pending; repeated submissions cannot create duplicate requests.
• Display the response message on success and HTTP errors, preserving values. Network or invalid-JSON failures show Could not submit. Try again. Allow retry, and ignore late responses after unmount.
• The stateless demo endpoint creates no account and stores no fields. It returns 201 for valid data and 409 for taken@example.com. Markup, validation message containers and basic styles are supplied.

Examples

Input: Submit empty fields
Output: Show validation messages without a request.

Input: Submit Maya Chen, maya@example.com and matching passwords
Output: Send normalized JSON once and display the demo response.