Trigger global search sync after static indexing

[bbbtttiii]

Problem

crds-net still indexes legacy static pages into the child Algolia static index (demo_crds_net_static / crds_net_static), but that work did not trigger a rebuild of the blended global search index afterward.

That meant static-page updates could be present in the child index while still being stale or missing in global_search_demo / global_search_prod.

Solution

After static-page indexing completes in crds-net, this change sends a follow-up request to sync-global-search-background in crds-unified with:

• slice=crds_net_static
• applySettings=false
• the current resolved environment (demo or prod)

This keeps the existing static indexing behavior in place, but adds the missing handoff so the global search index can rebuild from the updated static slice.

Corresponding Branches

Related search rollout work also exists in:

• crds-unified on prod/global-search-indexing
• crds-unified-components on prod/global-search-modal

Testing

Validate this change from the crds-net deploy/build logs.

What to verify in the build log

Look for the static indexing hook output in this order:

• Copied: ... -> _site_static/... for static page indexing
• Copying settings from 'crds_settings' to 'demo_crds_net_static'...
• Successfully copied settings from 'crds_settings' to 'demo_crds_net_static'
• Successfully indexed 11 records to Algolia index 'demo_crds_net_static'.
• [global-search-trigger] source=static env=demo status=...

What has already been validated

A deploy preview built from commit dc9a10b showed:

• 11 static pages were copied into _site_static
• settings were copied from crds_settings to demo_crds_net_static
• 11 records were successfully indexed into demo_crds_net_static
• the new global search callback executed

Current known gap

That same deploy log returned:

• [global-search-trigger] source=static env=demo status=404

This means:

• child static indexing is working
• the new callback is being attempted
• the receiving sync-global-search-background endpoint was not available on stable demo for that build

QA expectation for this PR

For this PR specifically, the important validation is:

• crds-net still successfully builds and indexes static records
• the new callback is attempted after indexing
• no static indexing regression was introduced

Follow-up validation after crds-unified is live on demo

Once sync-global-search-background is available on stable demo, rerun a crds-net build and confirm:

• the callback log changes from 404 to 200 or 202
• a known static page such as About Us, What We Believe, or Seven Hills exists in demo_crds_net_static
• that same page is then searchable in global_search_demo

[netlify]

✅ Deploy Preview for crds-jekyll ready!

Name	Link
🔨 Latest commit	dc9a10b
🔍 Latest deploy log	https://app.netlify.com/projects/crds-jekyll/deploys/6a187180a3b9570008c9303c
😎 Deploy Preview	https://deploy-preview-3546--crds-jekyll.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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