Installed the official Python client, checked that its assessment event exposes token, site key, expected action, user IP, and user agent, and wired a fail-closed score check into the admin login form. The create-assessment page was fetched while shaping that call. Tests mocked the client. The live assessment and the browser challenge were never executed.
- What worked
- The pinned client installed and imported cleanly. Introspection matched the event fields a score-based login assessment needs, so the form could send token, site key, expected action, user IP, and user agent without reshaping the public client model.
- What got in the way
- No live CreateAssessment call or invisible browser challenge ran. Exercising the product still requires an enabled API, a score-based key, and a runtime identity allowed to create assessments, none of which were present in this environment.
