Sign in
What the Screen Is For
Authenticate a console session by password or Google and handle provider challenges.
What It Shows and Lets People Do
The sign-in form uses SRP through the console provider and can continue to a new-password or authenticator challenge. Google uses the hosted provider hop with proof-key and state checks.
States and Errors
Local field problems and provider refusal are displayed through the form’s error components. The saved return destination is validated before protected navigation. Unknown accounts and wrong passwords share the implemented neutral sign-in response.
The state rows describe observed loading, empty, refusal or inactive handling where present. Linked validation rules belong to the planning layer; client feedback and authoritative service checks have distinct responsibilities.
Patterns It Must Respect
The pattern list names the built shared components and interaction patterns checked for this screen. This contract describes the existing screen; it supplies no replacement visual design.