2026-09-13 — Find accuracy nudge and Memphis land pins

Summary

Find search no longer silently trusts a coarse IP map center: home and map search surfaces a tooltip on the location-accuracy control asking guests to improve accuracy. Directory city pins for Memphis spread across land-safe metro hubs (not the river), unknown locations stay unpinned, and filtered result maps center on the result corpus.

Highlights

  • Header / hero search: bubble on the navigation-target control after a results search (and once per session on manual /find load) while precision is still IP-coarse — Use my location or Not now.

  • Navigation control is a real toggle: on = device GPS (fresh fix, no stale cache); off = restore the last IP seed. While the accuracy nudge is open the glyph stays inactive (muted); only the notification dot is primary.

  • After device or manual place is set, Find keeps that center — it does not yank the map to the search-result pin corpus.

  • Vercel IP geo (MaxMind) often places Memphis on/near the international airport; coarse city seeds and locality geocodes snap known cities to preferred downtown centers (Memphis → Court Square / downtown).

  • South-of-240 simulated hub sits in Whitehaven, not on MEM.

  • Memphis city-level / directory pins resolve at read time across Downtown, Midtown, East Memphis (east/west), south of I-240, Bartlett, Collierville, and Germantown; no stored pretend coords on seed insert.

  • Unknown location → no map pin; category search matches name tokens (e.g. Fried Chicken) instead of listing every nearby truck; filtered Find maps show matching pins (and recenter on their centroid only while still on coarse IP).