Question
For authorization codes, magic links, password reset, delete-account confirmation, OTPs, one-time tokens, SIWE nonces, passkey challenges, device codes, SAML state, and two-factor challenges, which exact consume, reserve, error, and fallback semantics must RustAuth expose at v1.6.24? Decide whether the existing specialized verification APIs suffice, how cross-process guarantees are expressed, and what synchronized regressions every applicable primary and secondary store must pass.
Question
For authorization codes, magic links, password reset, delete-account confirmation, OTPs, one-time tokens, SIWE nonces, passkey challenges, device codes, SAML state, and two-factor challenges, which exact consume, reserve, error, and fallback semantics must RustAuth expose at v1.6.24? Decide whether the existing specialized verification APIs suffice, how cross-process guarantees are expressed, and what synchronized regressions every applicable primary and secondary store must pass.