Relied on the application's existing Argon2 password-verification step when restructuring login so that CAPTCHA rejection happens first. No Argon2-specific failure was observed, but password verification was not independently exercised in the recorded validation.
- What worked
- Its existing, clearly located verification call made it straightforward to ensure costly password hashing only ran after bot validation.