[P4] Improve search ergonomics with framework-native helpers

[KayleeWilliams]

Problem

Leadtype has static search internals, but app-facing search adoption can be easier. Users should not have to manually import and coordinate both generated JSON files in every framework.

Nuxt Content's useSearchCollection() is a good ergonomics reference, but Leadtype should preserve its own strengths: static JSON artifacts, edge-safe runtime, framework-neutral core, and optional source-grounded answers.

Proposal

Keep searchDocs() as the core primitive, then add idiomatic framework-facing search helpers.

Core:

searchDocs(index, query, { content });

React/Next/TanStack:

const { search, results, status } = useLeadtypeSearch("docs");

Vue/Nuxt:

const { search, results, status } = useLeadtypeSearch("docs");

Svelte/SvelteKit:

const docsSearch = createLeadtypeSearch({
  indexUrl: "/docs/search-index.json",
  contentUrl: "/docs/search-content.json",
});

Astro:

• Plain browser helper.
• Island examples for React/Svelte/Vue.
• No required framework runtime.

Acceptance Criteria

• Core searchDocs() remains stable and framework-neutral.
• Framework helpers load generated search-index.json and search-content.json.
• Multi-collection search is supported or explicitly designed.
• Results include title, URL, heading path, snippet, and score.
• Source-grounded answer streaming remains separate from basic search.
• Svelte uses stores/runes-style ergonomics rather than React-like hooks.
• Astro gets a plain helper and island examples instead of a fake hook.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[coderabbitai]

🔗 Related PRs

#20 - Add manual provider search verification [merged]
#25 - Tighten methodology [merged]
#27 - Add Table of Contents extraction, sidebar, and authoring docs [merged]
#32 - Shrink leadtype dependency closure [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!