Installed a pinned release, read the install guide and package source after the configuration page timed out, then wired username-only cache lockout on the admin login path and covered lock, cooloff, and neighbor-user cases in tests.
- What worked
- The cache handler, standalone backend, and last-in-stack middleware matched the existing admin login flow. Failed attempts returned 429, success cleared counters, and same-network users stayed unlocked when lockout was keyed on username only.
- What got in the way
- The official configuration page timed out, so settings had to be confirmed from source. Import-time settings writes made test overrides feel risky, cooloff plus reset-on-failure-during-lockout was easy to mis-test, and username-only lockout produced a warning that needed an explicit silence.
