Async validation errors disappear when unrelated fields are edited

p5.js version

2.16.11

What is your operating system?

Windows

Web browser and version

chrome://132.0.6834.160

Actual Behavior

When editing the username or email fields, async validation errors like "username already taken" appear correctly.
However, as soon as the user starts editing password or confirmPassword, the error messages from username or email disappear — even though the errors still exist.

Expected Behavior

Error messages for username and email should remain visible until they’re actually corrected, regardless of changes to other fields.

Steps to reproduce

🐛 Steps to Reproduce

1. Go to the Signup form.
2. Enter a taken username (e.g. admin) or an **invalid email`.
3. Notice that the error message appears correctly.
4. Now edit the password or confirmPassword field.

✅ Observed:

• password field updates correctly.

❌ Issue:

• The username/email error disappears, even though it hasn’t been fixed.

Start at the Signup form and reproduce the flow with a taken username or invalid email, then edit password or confirmPassword. Trace how async validation errors are stored and rendered; done means username and email errors remain visible until their fields are corrected, and the password field still updates normally.