Console command palette (⌘K) doesn't surface record search hits though /api/v1/search returns them #3371

Found dogfooding a downstream app on 16.0.0-rc.1; confirmed the backend is fine against a local framework checkout, so this is a console/objectui client bug.

Symptom

In the Console command palette (⌘K), searching a well-known record name returns no records — only an unrelated report. E.g. typing Wayne (with a Wayne Enterprises account and a Wayne Q1 Expansion opportunity in the org) returns just a 报表 / Lead Inflow report row; the account/opportunity never appear.

The backend works — this is client-side

Calling the search API directly from the authenticated page returns the record correctly:

GET /api/v1/search?q=Wayne  → 200
{"query":"Wayne","hits":[{"object":"crm_account","id":"…","title":"Wayne Enterprises",
  "snippet":"Wayne Enterprises","record":{ …"account_number":"ACC-000005"… }}]}

?q= and ?query= both return hits; the search service (PinyinSearchPlugin) is registered and metadata-protocol searchAll (packages/metadata-protocol/src/protocol.ts) resolves records. So /api/v1/search is healthy — the command palette is not calling it / not surfacing its hits, and instead only lists metadata (reports/views).

Impact

For a CRM this is a core-flow miss: reps expect ⌘K → type a customer/deal name → jump to the record. Today record lookup via global search is effectively broken while the backend can serve it.

Ask

Wire the Console command palette to /api/v1/search (q= param) and render record hits grouped by object, alongside the existing metadata results. (Filing here per the platform-issue process; route to objectui if that is where the palette lives.)