Search nearby events

Stage 196: real nearby events for a category label (e.g. "Music", "Comedy", "Sports" — an unrecognized label maps to a sensible default rather than erroring, same as every other caller of searchNearbyEvents), merged from up to four real sources: Ticketmaster (onsale-only), first-party user/organizer submissions, official city open-data event calendars, and events found directly on a business's own site (schema.org/JSON-LD or a real RSS/iCal feed) — see the NearbyEvent schema's origin/originLabel fields. Each of the three free, first-party origins carries a detailUrl to a real, permanent LocalSelections event page when it clears that page's own content floor (null otherwise); a ticketmaster-origin result never gets one (see the NearbyEvent schema's detailUrl note) — use its ticketUrl instead. This is the same shared, rate-limited Ticketmaster pool every other event-consuming endpoint draws from (Stages 165/167) — a burst of calls can return a 503 high_demand (the pool-wide daily ceiling) or a 429 rate_limited (this caller's own per-day cap on uncached lookups) in addition to the usual v1 429. Requires the events scope. Costs 2 units of the key's rate-limit budget per call. Stage 198: a free-tier key is also separately capped at 80 calls/day to this endpoint specifically, on top of all of the above (see the 429 response) — commercial use is exempt.