feat(aixy): add curated 50-model catalog

[oscarcpozas]

Summary

• Add 49 curated routes, bringing the Aixy catalog to exactly 50 models including the existing GPT-4.1 Mini entry.
• Cover recent non-deprecated models from 13 labs without mirroring complete upstream inventories.
• Prefer first-party Aixy routes; use a small OpenRouter selection for current models without a direct route.
• Keep availability tenant-specific and BYOK. This PR adds catalog TOMLs only and does not add bulk sync automation.

Selection

• OpenAI: 11
• Anthropic: 8
• Google: 6
• Zhipu AI / GLM: 2
• Alibaba / Qwen: 5
• DeepSeek: 2
• Mistral: 5
• Meta: 3
• xAI: 4
• ByteDance Seed, MiniMax, Moonshot AI, and NVIDIA: 1 each

Source mapping

• Model identity, capabilities, and default limits inherit through base_model from the canonical lab entries already reviewed in models.dev; the Aixy files keep only host-specific deltas.
• Direct routes mirror the established first-party provider surfaces: OpenAI, Anthropic, Gemini, Alibaba Model Studio, DeepSeek, Mistral, and xAI.
• The five OpenRouter-prefixed routes use OpenRouter's authoritative model API for IDs, pricing, limits, and supported parameters, plus its reasoning controls.
• The zero-cost Meta Llama routes reflect Meta's officially announced limited free Llama API preview; availability remains credential- and project-scoped.
• Aixy's integration contract and authenticated catalog behavior are documented in the Aixy integration guide.

Validation

• bun validate
• 50 resolved Aixy models
• 0 deprecated or beta routes
• All 44 reasoning models define provider-appropriate reasoning_options

This replaces the earlier bulk-generated approach. #5507 remains closed.

[github-actions]

Action items

• [high] [possible mistake] providers/aixy/models/openrouter/nvidia/nemotron-3-ultra-550b-a55b.toml:19 - Check: OpenRouter-prefixed Aixy routes should match OpenRouter peer pricing/limits when the PR cites OpenRouter as the source. Why: This file sets cost to 0.6/3.6/0.2 and limit to context 512_288 / output 461_059, while providers/openrouter/models/nvidia/nemotron-3-ultra-550b-a55b.toml uses 0.625/3.125/0.1875 and 262_144/32_768. Those are material catalog differences for the same claimed upstream. Action: Align cost and limits with the OpenRouter peer (or document/prove an Aixy-specific OpenRouter quote that differs).
• [medium] [possible mistake] providers/aixy/models/openrouter/z-ai/glm-5.3.toml:3 - Check: OpenRouter-route overrides must match OpenRouter peer capability/limit data unless Aixy truly differs. Why: Aixy sets structured_output = false and limit.context = 1_048_576, but the lab base is structured_output = true / context 1_000_000 and the OpenRouter peer inherits structured output and uses context 1_310_720 with no structured_output = false override. Action: Drop or correct structured_output and limit.context to match the OpenRouter peer (or provide evidence that Aixy’s OpenRouter-backed route actually differs).

[oscarcpozas]

Addressed both review findings in 11d2c64a5:

• aligned Nemotron 3 Ultra pricing and limits with the current OpenRouter peer;
• removed the contradictory GLM 5.3 structured-output override and aligned its context limit;
• checked all five OpenRouter-backed Aixy routes against current dev; they now match their OpenRouter peers exactly.

bun validate and all 23 SDK tests pass locally.

[github-actions]

No actionable findings.