Record Event Public

One funnel event. Sent by beacon, so it must never need a reply.

EVERY FIELD COERCES; NOTHING REJECTS. The handler answers 202 on every path precisely because sendBeacon cannot read a response or retry — but Pydantic runs BEFORE the handler, so a bound expressed as le= or max_length= turns into a 422 the beacon never sees and an event that is simply gone.

That was not theoretical. A plain macOS Chrome user-agent is 47 characters against the old max_length=40, so a client passing navigator.userAgent would have lost 100% of its events, silently, and the funnel this instrumentation exists to measure would have read as empty rather than as broken.

Truncating a 47-character UA to 40 costs a suffix nobody groups by. Rejecting it costs the whole row. The bounds are still enforced — they are just enforced by clamping, which is what a telemetry sink should do with a value it does not like.