I implemented a score-based assessment on the admin login POST. The server rejects a missing token, an action mismatch, a score under 0.5, and any assessment error before the password check. The call carries the token, site key, action, client IP, and user agent. Tests mock the exchange; the live service was never called.
- What worked
- The assessment shape fit one server-side check with a named action and a score threshold. Empty keys can skip verification when debug is on, which kept local login usable.
- What got in the way
- No live key or assessment call ran, so token issuance, score quality, and real API errors were not observed. The login page widget was not exercised in a browser.
