[diegosouzapw]

Closes #4164

Problem

OmniRoute ships a zero-setup auto/* catalog (auto/best-coding, auto/best-reasoning, auto/pro-coding, … — 16 AUTO_TEMPLATE_VARIANTS in open-sse/services/autoCombo/builtinCatalog.ts) that the dashboard advertises and that resolve on demand via createBuiltinAutoCombo. But /v1/models (src/app/api/v1/models/catalog.ts) only emitted persisted DB combos + provider models, so clients that build their model picker from /v1/models — e.g. Hermes Agent (hermes model) — never saw any auto/* option.

Fix

The catalog now emits every AUTO_TEMPLATE_VARIANTS id (as owned_by: "combo") at the top of the list, before persisted combos and provider models. A shared listedIds set dedupes them so a persisted user combo can't shadow or double a built-in auto/* id.

Showing each auto/*'s dynamically-selected members (the reporter's secondary ask) is a separate enhancement — those are resolved per-request by the 9-factor scorer and have no fixed membership to list.

Test (TDD, Hard Rule #18)

tests/unit/models-catalog-auto-combos-4164.test.ts:

• every AUTO_TEMPLATE_VARIANTS id is advertised (imports the source-of-truth list, so it can't drift);
• the auto/* entries sit at the top of the list;
• auto/* ids are unique.

RED 2/3 → GREEN 3/3. Catalog route regression 45/45 (aligned the existing 'context_length for individual chat models' test to exclude owned_by: "combo" entries — combos/routers resolve dynamically and have no fixed context_length, so they are categorically not individual chat models; this is alignment, not masking). typecheck:core, eslint, check:file-size clean. The failing vitest ecosystem.test.ts › model catalog is environmental (ECONNREFUSED :20128, needs a live server), not from this change.

[gemini-code-assist]

Code Review

This pull request advertises the built-in, zero-setup auto/* combos at the top of the /v1/models endpoint listing to ensure clients can discover them, while also preventing duplicates from shadowing persisted database combos. It includes comprehensive unit tests to verify this behavior and updates existing tests accordingly. The reviewer noted a minor improvement opportunity to remove a redundant check inside the loop that populates the auto/* variants, as the set is empty at initialization and the keys are already unique.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The check if (listedIds.has(autoId)) continue; is redundant here. listedIds is initialized as an empty Set immediately before this loop, and Object.keys(AUTO_TEMPLATE_VARIANTS) returns unique keys. Therefore, listedIds.has(autoId) will always evaluate to false during this loop. We can safely remove this check to simplify the code.

Suggested change

	if (listedIds.has(autoId)) continue;
	listedIds.add(autoId);
	listedIds.add(autoId);