Saved search from Places view doesn't render map markers when restored

[jamiefolsom]

Summary

A user can save a search from the Places explore view, but when the saved search is restored, the results list populates correctly while the map shows no markers. May be related to the fuzzy-places / certainty-radius feature (#607, #612, #614).

Observed on

• Marronage staging (deploy/marronage branch)
• URL: https://marronage.staging.performant.studio/en/search/places/

Reproduction steps

1. Go to the Places search view
2. Apply any filter (e.g., a Country facet selection) or let the default query run
3. Click "Save search" and give it a name
4. Navigate to Saved Searches and open the saved one

Expected

The map renders the same set of markers (and certainty radii) that were visible when the search was saved.

Actual

The map renders the base layer but no place markers or radii. NB: the table and timeline views work, and show data.

Notes

• Could be timing (map layer tries to read results before they're populated from the session store)
• Could be the new "hide point when certainty radius present" logic on Hide point when certainty radius is present #614 failing to render the radius at all when coming from a restored session
• Console contains 404 errors; see sample saved search. https://marronage-staging.netlify.app/en/sessions/search/53919d62-8ad6-4081-8d27-1abcd6bb9790#map=1/0/0

[jamiefolsom]

Diagnosed and patched in #618.

Root cause: SaveButton.tsx writes features to the session; on restore, Map.tsx calls fetchGeometry(uuid) per feature. That hits the prerender = true /api/geometry/[uuid].json route, whose getStaticPaths enumerates the geometry Astro content collection. The collection is only registered in content.config.ts when PRELOAD_MAP=true && !USE_CONTENT_CACHE — marronage (and any default server-mode deploy) has neither set, so every request 404s. Table and timeline views are unaffected because they do not call fetchGeometry.

Fix: rebuild features from the saved hits via TypesenseUtils.getFeatures (same path the live search page uses); drop the features array from the saved payload. Existing saved sessions render correctly without re-saving.