Fix coordinate handling in nearby event and communities map

[RisingOrange]

This fixes two coordinate-handling issues: NearbyEvent now passes coordinates to @turf/distance in the correct [longitude, latitude] order, and both NearbyEvent and the communities map now handle valid 0 latitude/longitude values correctly.

Summary

• fix NearbyEvent to pass coordinates to @turf/distance in [longitude, latitude] order
• fix NearbyEvent null checks so valid 0 latitude/longitude values are handled correctly
• fix the same 0-value edge case in the communities map initial state

Why

NearbyEvent was building @turf/distance coordinate tuples as [latitude, longitude], but Turf expects GeoJSON order: [longitude, latitude].

It was also using falsy checks for coordinate presence. In edge cases, that can treat valid coordinates like 0 latitude or 0 longitude as missing.

The communities map had the same edge case when initializing the map center and zoom from the user location.

Evidence

• Turf distance docs use coordinate examples in [longitude, latitude] order:
  https://turfjs.org/docs/7.2.0/api/distance
• GeoJSON RFC 7946 states: "The first two elements are longitude and latitude, or easting and northing, precisely in that order."
  https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.1

Notes

• The existing MapLibre code in src/routes/communities/+page.svelte already follows [lng, lat] ordering, which was a useful internal consistency check.
• pnpm check passes.

[netlify]

✅ Deploy Preview for pauseai ready!

Name	Link
🔨 Latest commit	8b93a99
🔍 Latest deploy log	https://app.netlify.com/projects/pauseai/deploys/69bd3ffaf13439000858619d
😎 Deploy Preview	https://deploy-preview-693--pauseai.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 86 (🟢 up 1 from production) Accessibility: 90 (no change from production) Best Practices: 92 (no change from production) SEO: 99 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Wituareard]

Wait what? I guess it kinda worked before because both sides had the wrong order? Tysm, could you do some testing with the preview by overwriting the geo response? I'm not available atm

[RisingOrange]

@Wituareard Okay, I'll do some more tests and add testing instructions

[RisingOrange]

I tested the preview by overriding the geo and calendar responses in the browser, and the nearby-event banner shows correctly with the fix in place.

To sanity-check, I also compared the same intended locations in a distance calculator, once with the coordinates entered in the correct order and once with them swapped. With the correct [longitude, latitude] order, the distance stays below the 100 km threshold, but with the swapped interpretation it goes above 100 km.

Correct order: distance is below 100 km

Swapped order: distance is above 100 km