Contact Form

Same pattern as comments. A form, a URL, a log entry.

The flow

1. Visitor fills out contact form → GET /events/contact/submit?name=...&email=...&message=...
2. CloudFront logs it. Returns 202. Done.
3. You check when you want: grep contact/submit in the logs.

No email service. No form backend. No third-party widget. No spam filter needed — you read the log when you feel like it.

Why it works

The events endpoint already exists. The CloudFront Function already returns 202. The logs already capture the full query string. Adding a contact form is adding a form. Zero infrastructure.

The email field

It's @pii in the schema. The MCP log reader won't show it. You see it when you grep directly. The visitor trusts you with their email — not your tools.