Signup and verification

Task sequence

• Enter name, email and a password of at least eight characters.
• Submit to create the pending account.
• Read the inbox-confirmation prompt.
• Follow the verification email, then sign in.

Data and persistence

The source creates a user and bcrypt credential, hashes an email token and gives it 24-hour expiry, then calls Brevo. Verification handling and optional Kit sync are separate source integrations. The capture replaces the request with local success and sends no email.

Failure and recovery

Existing addresses yield conflict; short passwords are rejected. Provider failures and partial writes need operational recovery beyond the UI. Google markup is hidden in the source.

Acceptance criteria

• Email fields are associated with labels.
• Confirmation copy is not a receipt assertion.
• Offline screenshots exclude Turnstile rather than falsely showing verification passed.

Source references