The sign-in page component renders the widget container and loads the captcha script only on that page. Over HTTP, server responses for a missing token, a rejected token, and a disabled production configuration matched the intended states. Client-side script startup was not observed.
- What worked
- Server rendering left the widget hook in the HTML, and the form kept posting the captcha field through the existing action.