console: ⌘K / full-page search scope silently truncated to the first 8 nav objects #3047

Symptom

⌘K global search (and the full-page search) can only find records in a subset of the app's objects. Searching an existing record code returns "no results", while the same query against GET /api/v1/search directly (with that object in objects, or with no objects param) matches — the backend index is fine; the UI truncates the scope it requests.

Root cause

useRecordSearch slices its candidate pool to maxObjectsQueried (default 8). That cap is meant to bound the per-object fanout fallback, but it was applied to the pool itself — so the objects whitelist sent to the single-request /api/v1/search only ever named the first 8 nav objects. Which sidebar group happens to come first decides which records are findable; in an app with 40+ searchable objects the rest are unsearchable no matter what the user types, and searchableFields configured on those views is dead weight.

Expected

The searchAll path must send the full app whitelist; the parallel-request cap applies only to the per-object fanout fallback.

Found via real-app dogfooding (os-tianshun-ehr platform defect registry PLAT-DEF-023, on 17.0.0-rc.0).