Check a registration step's answer for its refusal, as a typed failure of
the step that sent it.
Detection logic (two error types):
No-ft error: bloks_payload has no ft — gs entries contain error details directly
(e.g. CAA_REG_CONTACTPOINT_PHONE:error_message = "Mobile number required.")
With-ft error: bloks_payload has ft, but the action executable sets
should_show_error to true via a global state mutation. The error message
is also set in the executable (e.g. "That code isn't valid.").
Only an executable that sets should_show_error: true under the step's
prefix is a refusal; challenge and spam markers among the answer's string
literals then pick RegistrationChallengeRequiredError or
RegistrationSpamError over the step's own error.
Check a registration step's answer for its refusal, as a typed failure of the step that sent it.
Detection logic (two error types):
No-ft error: bloks_payload has no
ft— gs entries contain error details directly (e.g.CAA_REG_CONTACTPOINT_PHONE:error_message = "Mobile number required.")With-ft error: bloks_payload has
ft, but theactionexecutable setsshould_show_errortotruevia a global state mutation. The error message is also set in the executable (e.g."That code isn't valid.").Only an executable that sets
should_show_error: trueunder the step's prefix is a refusal; challenge and spam markers among the answer's string literals then pick RegistrationChallengeRequiredError or RegistrationSpamError over the step's own error.