The 451 login answer escalates to last-resort account recovery through the
ap.two_step_verification.entrypoint_async action (HTTP 200, no session):
the app continues with that action (AccountRecoveryBloksEntrypoint) and
shows the code-entry screen it opens ("Check your email"). The error is the
login's server-decided outcome, so the caller can continue without reading
the answer again. This is the recorded 451 path; the older dialog with
has_identification_error and a challenge_picker Continue stays modelled
separately.
The 451 login answer escalates to last-resort account recovery through the
ap.two_step_verification.entrypoint_asyncaction (HTTP 200, no session): the app continues with that action (AccountRecoveryBloksEntrypoint) and shows the code-entry screen it opens ("Check your email"). The error is the login's server-decided outcome, so the caller can continue without reading the answer again. This is the recorded 451 path; the older dialog withhas_identification_errorand achallenge_pickerContinue stays modelled separately.