## Summary
Follow-up to PR #12 / Lighthouse agentic-browsing audit on `/contact` (score 0.88).
- Add `toolparamdescription` to all contact form fields for WebMCP schema validity
- Move reCAPTCHA outside the annotated `<form>` so `g-recaptcha-response` is excluded from the declarative tool schema
- Always render `toolname` / `tooldescription` on the contact form (not gated by `WEBMCP_ENABLED`)
- Override `django_recaptcha/widget_v3.html` to associate captcha with `form="contact-form"`
- Update docs with HTTPS Lighthouse commands
## Test plan
- [x] `python manage.py test public.tests` — 21 tests pass
- [ ] Deploy and re-run Lighthouse agentic-browsing on `https://aimloperations.com/contact`
- [ ] Confirm `webmcp-schema-validity` passes (expected overall score 1.0)
Expose public marketing actions as navigator.modelContext tools behind WEBMCP_ENABLED, including contact submission and service navigation helpers with docs and regression tests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Follow-up to PR #12 / Lighthouse agentic-browsing audit on
/contact(score 0.88).toolparamdescriptionto all contact form fields for WebMCP schema validity<form>sog-recaptcha-responseis excluded from the declarative tool schematoolname/tooldescriptionon the contact form (not gated byWEBMCP_ENABLED)django_recaptcha/widget_v3.htmlto associate captcha withform="contact-form"Test plan
python manage.py test public.tests— 21 tests passhttps://aimloperations.com/contactwebmcp-schema-validitypasses (expected overall score 1.0)e2e93e962eto16fb5e4350