[v3.8.50] feat(ui): add global model search to Combo builder

[corefusiion]

Summary

• Added a new Global Model Search feature to the Combo Builder (/dashboard/combos).
• Previously, when searching for a model, users were restricted to viewing models available from the currently selected provider.
• This new feature adds a "Busca Global" (Global Search) toggle. When enabled, it searches for the model across all configured providers simultaneously, drastically improving the user experience when hunting for specific models like Claude or GPT across multiple APIs.
• Included UI feedback when no models are found.

Related Issues

• Related to UI/UX improvements in the Combo Builder.

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• No specific tests added, as this is purely a frontend visual/filtering feature reusing existing model states.

Coverage Notes

• This PR changes frontend files in the dashboard (src/app/(dashboard)/dashboard/combos/page.tsx). No backend or routing logic was changed.

[corefusiion]

Summary

• Added a new Global Model Search feature to the Combo Builder (/dashboard/combos).
• Previously, when searching for a model, users were restricted to viewing models available from the currently selected provider.
• This new feature adds a "Busca Global" (Global Search) toggle. When enabled, it searches for the model across all configured providers simultaneously, drastically improving the user experience when hunting for specific models like Claude or GPT across multiple APIs.
• Included UI feedback when no models are found.

Related Issues

• Related to UI/UX improvements in the Combo Builder.

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• No specific tests added, as this is purely a frontend visual/filtering feature reusing existing model states.

Coverage Notes

• This PR changes frontend files in the dashboard (src/app/(dashboard)/dashboard/combos/page.tsx). No backend or routing logic was changed.

[diegosouzapw]

Thanks for this — global model search across all providers in the Combo Builder is a genuinely useful addition and the core logic in combos/page.tsx reuses the existing buildPrecisionComboModelStep/hasExactModelStepDuplicate helpers correctly.

Three things need to be fixed before this can merge; the maintainers can apply these directly in your branch if you'd rather not:

1. pnpm-lock.yaml (26,111 lines) shouldn't be in the diff. This repo is npm-based (npm workspaces + package-lock.json); the tracked pnpm-workspace.yaml/pnpm.json are unrelated pre-existing config for a Bun compatibility path, not evidence pnpm is used here. Please drop that file (likely generated by running pnpm install locally instead of npm install).

2. i18n: the new UI introduces several Portuguese-only strings with no translation path — the search placeholder, "Atalhos:", "Adicionar Todos (...)", "Nenhum modelo encontrado...", "Provedor:"/"conta(s)", "Adicionado"/"Adicionar" are raw PT literals, and even the two labels that do call getI18nOrFallback() (builderModeStep, builderModeGlobal) use Portuguese fallback text instead of the English-fallback convention every other label in this file follows. None of these keys exist yet in any of the 43 files under src/i18n/messages/. Since the dashboard supports many locales, these need real i18n keys + an English fallback, with translations added like every other string in that file.

3. Tests: per this repo's bug/feature policy, changed production code needs a test. There's currently no test at all for the new search/filter/dedup logic (allGlobalModels, filteredGlobalModels, handleAddGlobalModelStep, handleAddAllGlobalSearchMatches) — a small vitest covering "search matches across providers" and "add-all skips duplicates" would do it.

Optional nit: the assembleStandalone.mjs Windows src===dest guard looks like a reasonable, unrelated defensive fix — happy to keep it bundled, just flagging it's untested and off-topic from the main feature.

Nothing here is a rejection of the idea — the feature itself is worth having, it just needs these three items addressed first.

[diegosouzapw]

⏸️ Ejetada do merge-train — placeholders __MISSING__ nas traduções

Esta PR foi ejetada do trem local do v3.8.49 e adiada para o v3.8.50. O gate tests/unit/i18n-vi-completeness.test.ts falha no resultado combinado:

✖ Vietnamese locale has no internal missing markers or empty fallbacks
  AssertionError: Expected values to be strictly deep-equal:
  + [
  +   { key: 'combos.builderModeStep',
  +     value: '__MISSING__:Step by step (Provider → Model)' },
  +   { key: 'combos.builderModeGlobal',
  +     value: '__MISSING__:Global model search (Custom combo)' },
  +   { key: 'combos.builderGlobalSearchPlaceholder',
  +     value: '__MISSING__:Search models across all providers (...)' },
  ...

Causa

As 10 chaves novas do Combo builder foram adicionadas aos arquivos de locale com o marcador literal __MISSING__:<texto em inglês> como valor, em vez da tradução. O gate de completude do vietnamita rejeita exatamente esse marcador — ele existe para impedir que placeholders cheguem à UI do usuário final.

Verificação

Trem	i18n-vi-completeness
com esta PR	❌ 4/5 — 10 chaves com __MISSING__
sem esta PR	✅ 5/5

Confirmei também que na base (origin/release/v3.8.49) o teste passa 5/5 — ou seja, o marcador entra com esta PR, não é dívida pré-existente.

Para destravar

Substituir os placeholders pela tradução real das 10 chaves nos locales afetados. Não basta remover o prefixo __MISSING__: e deixar o texto em inglês — isso passaria no gate mas colocaria inglês num arquivo de tradução, que é justamente o que o teste existe para evitar.

O resto da PR está bom: os 48 arquivos foram auditados chave-a-chave (delta exato de +10 chaves-folha por locale, nenhuma chave da release perdida), o conflito de import em combos/page.tsx foi resolvido, typecheck:core limpo e combo-builder-draft.test.ts 14/14. É só a questão das traduções.

[diegosouzapw]

Re-homed to release/v3.8.50: v3.8.49 entered its release freeze, so the branch now belongs to the release captain and development continues on the next cycle. Nothing is wrong with this PR — it just needed a live base. No action needed from you; CI will re-run against the new base.