Accept API hits in navigation-search schemas

[reakaleek]

Navigation-search and Codex modal hooks now parse mixed docs and api hits. The store type filter matches the indexed docs value.

Affects: Site UI, Search

Prompt summary: Ship the Jump to page API story as stacked PRs. This first PR is the root on main and covers elastic/docs-eng-team#857: accept api hits, fix the store type union, and align the mock service.

Stack: 1 of 5, root on main. Later PRs for elastic/docs-eng-team#858 through elastic/docs-eng-team#861 stack on this branch.

Why

A navigation-search hit with type: "api" fails Zod parse and drops the whole response. The store filter still uses doc, which never matches the indexed value docs. Local mock results use the same stale value, so a type=docs query returns nothing.

Closes elastic/docs-eng-team#857

What

Result schema

Both query hooks accept docs and api on each hit. A mixed response now parses instead of throwing.

Type filter

TypeFilter is 'all' | 'docs' | 'api'. A later type=docs query can match indexed documents.

Mock results

MockNavigationSearchService emits Type = "docs" so local filtered queries match the same contract.

Verify

cd src/Elastic.Documentation.Site && npm run test
# SearchResponse parses a mixed docs and api navigation-search response
# stores docs and api filters, never doc

Out of scope: Mounting the box, the type attribute, API-shaped rows, and leftover cleanup. Those land in the stacked PRs above.

Made with Cursor

[github-actions]

Docs preview (local build)

Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4143/

[github-actions]

Approved: no actionable issues found in this diff.

---

What is this? | From workflow: PR Review

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.