Create a user without premature validation errors

User intention

Add a new user.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Open Create new user through reauthentication and inspect the empty Username field before editing it.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Inspect the initial Username border, then compare empty and malformed submissions, correction, and the resulting user list.

How is it judged?

01 · Given

Restore the data and starting state.

The person is logged in as the environment-provided admin, on Display settings with the Origine theme selected, and has not opened or interacted with the Create new user form in this browser session.

02 · When

Perform the interaction.

The person clicks Manage users, then enters the admin password and clicks Login at the required reauthentication prompt, opening Create new user without focusing or changing any of its fields.

03 · Judge

Rationale: An empty field is a normal starting state before the administrator has entered a username. Error styling should identify an invalid attempt and clear after correction, helping the user complete account creation without weakening validation.

Require

The untouched Username field must initially appear neutral. Preserve required-field and format validation: empty or invalid submissions must remain blocked with visible field feedback. After valid correction and leaving the field, clear its error indication. Valid account creation must remain available.

Allowed

Equivalent CSS or interaction-state implementations are acceptable; no particular pseudo-class or reference patch is required.
Normal focus indicators, required-field indicators, labels, layout, language/time-zone defaults and administrator reauthentication may remain unchanged.
Different error colors or treatments and native browser validation feedback are acceptable if they communicate an actual validation failure and support correction.
Validation may appear after meaningful invalid-field interaction or a submission attempt according to the supported browser behavior; merely focusing and leaving an unchanged empty field need not trigger a specific error style.