[MumuTW]

Summary

Second slice of the accepted direction in #2979 (pairs with #11685 autoSync default and #11688 reactive discovery trigger). Two gaps closed:

1. Bare-name resolution no longer needs hand-written aliases for new Antigravity-family models. The backend advertises tiered ids (gemini-3.7-flash-high/medium/low) while users naturally call the bare base name; Gemini 3.7 Flash shipped with no alias, so bare names mis-routed until the catalog was re-frozen by hand. New src/lib/providerModels/syncedAutoAliases.ts derives bare-base → default-tier (high > medium > low) aliases from the synced discovery catalog — in memory, no persistence, always consistent with the latest sync. Merged at the LOWEST precedence in getCombinedModelAliases: explicit DB/settings/wildcard aliases always win. A base that is itself callable gets no alias; agy wins over antigravity for the same base.
2. Discovery-advertised token windows now survive to the enforcement chain. The [BUG] OMNIROUTE_DISABLE_CREDENTIAL_HEALTH_CHECK still logs scheduler started #11016 reconcile already trusts synced inputTokenLimit at request time, but the Antigravity discovery normalizer dropped every field except id/name — so nothing ever carried limits. The normalizer (and the client mapper) now forward inputTokenLimit/outputTokenLimit (also probing contextWindow/maxOutputTokens spellings). Extraction is defensive: absent/non-numeric fields yield nothing, so payloads without limits change zero behavior.

Related Issues

• Related to [Feature] Automatically Discover & Sync Models from Providers (Remove Hardcoded Model Lists) #2979 (accepted background discovery/sync direction — slice 2 of 3)
• Related to feat(oauth): default Antigravity-family connections to model auto-sync #11685 (autoSync default), feat(models): reactive discovery sync after Antigravity model-not-found 404 #11688 (reactive discovery trigger), [BUG] OMNIROUTE_DISABLE_CREDENTIAL_HEALTH_CHECK still logs scheduler started #11016 (synced token-limit enforcement chain), fix(providers): discover live AGY models #8123 (live AGY discovery)

Validation

• Change type: provider
• Focused tests: node --import tsx/esm --test tests/unit/synced-auto-aliases.test.ts → 10/10 pass (pure derivation rules, limits extraction edge cases, live synced-catalog integration with a real temp-DATA_DIR sqlite + active connection fixture)
• Regression: antigravity-model-aliases, 8958-alias-backed-node-prefix, 9034-alias-backed-prefix-id-repro → pass
• npx eslint: no NEW issues on touched files (model.ts carries two pre-existing localDb no-restricted-imports errors from the frozen CI error set — untouched by this PR)
• node scripts/check/check-file-size.mjs → OK
• Reconciled with current main (v3.8.50)
• Production-code changes include new automated tests in this PR

Tests Added Or Updated

• tests/unit/synced-auto-aliases.test.ts (new, 10 tests): tier grouping + high-tier default; medium/low fallback; callable-base skip; non-tiered ignore; provider precedence; empty inputs; limits extraction (numeric, alternate spellings, junk rejection); client-mapper passthrough; live synced-catalog read via real sqlite fixture.

Coverage Notes

syncedAutoAliases.ts fully covered. normalizers.ts changes covered by the extraction tests (both payload shapes exercised). model.ts merge order covered indirectly by the alias regression suite (explicit aliases still resolve) plus the derivation tests.

Reviewer Notes

• Alias precedence: auto < DB-namespace < settings exact < settings wildcard. Worst case for a bogus auto-alias is a shadowed bare name; explicit aliases override it immediately.
• No DB writes, no schema change, no new settings — derivation is read-only over the existing synced store.
• If the Antigravity payload field names differ from the probed spellings, limits simply stay absent (no-op) — extend extractDiscoveryTokenLimits when the real shape is confirmed.

[diegosouzapw]

Thanks for this! Its base (main) had diverged too far from the active release/v3.8.51 for a
clean retarget, and this fork rejects maintainer pushes, so a direct rebase-and-merge wasn't
possible. Recreated your commit (author preserved via cherry-pick) onto the current tip and
merged as #11889 — thank you for closing out the synced auto-aliases + token-limits slice.