Installed the Django adapter, used its field, widget template, HMAC settings, and collected static script on the admin login form. A challenge only after failed attempts is not a built-in mode, so custom form logic sat on top. README and package metadata were enough to start; tests needed package internals.
- What worked
- The widget rendered from first-party static files, HMAC defaulted to the Django secret, and replay rejection worked in tests once cache was configured. Pinning via the package index was straightforward.
- What got in the way
- There is no delayed-until-N-failures mode, so visibility and validation had to be hand-wired. Generating valid test solutions required inspecting the installed adapter and the underlying solver rather than a documented test helper. The widget was not clicked in a real browser in this session.