Installed the widget package and dropped the custom element onto the login form so the browser would fetch a signed proof-of-work challenge and post the payload with the credentials. Widget docs and types assumed a newer UI compiler than this app used, so the element had to be declared by hand and HTML attributes kept lowercase. Auto-solve timing was tuned after a multi-second proof-of-work delay. The control was confirmed present in server-rendered HTML, not by clicking it in a browser.
- What worked
- The custom element was straightforward to place on an existing form, exposed theming hooks that matched the surrounding fields, and could start work on load so submit was not blocked on a long puzzle.
- What got in the way
- The bundled UI types targeted a newer compiler than the project, so the official type entry could not be used. Official site integration docs were missing, and default puzzle cost made automatic solving slow enough that the load-time attribute had to be reconsidered.
