[Leo310]

Fixes #480.

Problem

Model labels, context windows and capability flags come from a models.dev catalogue lookup (lookupModelInfoSync). Its last tier was a Levenshtein match over separator-stripped tokens (distance ≤ 2). One-edit tolerance is wrong for model ids, where a single character carries meaning: qwen3.8 normalizes to qwen38, one edit from the catalogue's qwen38b, so a custom-provider model was renamed to "Qwen 3 8B" and silently inherited that model's context window and vision/tool/reasoning flags. The existing digit-sequence guard was already patching one instance of this; a size suffix is the same class of problem and can't be special-cased exhaustively.

Reproduced against the live catalogue with a custom provider id:

Typed id	Before	After
qwen3.8	Qwen 3 8B (wrong)	unchanged
qwen3:8b	Qwen 3 8B	Qwen 3 8B
claude-sonet-4-5 (typo)	Claude Sonnet 4.5	unchanged

Change

• Remove the Levenshtein tier. Exact, provider-prefixed and separator-insensitive (normalized equality) matching stay, so qwen3:8b / Qwen3-8B / qwen/qwen3-8b still resolve to the same entry.
• The only lost behaviour is typo recovery, which had no real value: ids normally come from the provider's model list, and a typo'd id fails at request time anyway. Recovering the label only hid the mistake.
• Tests: retarget the two assertions that asserted fuzzy hits, add a separator-variant case and a qwen3.8 regression case.

Not disabling the lookup for custom providers: OpenAI-compatible endpoints (Groq, Together, SAP AI Core) get correct metadata from exact and normalized matches, and the cross-provider precedence tests cover exactly that.

Checks

bun run check, bun run format, bun run lint, bun run test (1675 passed).

AI assistance: written with AI coding agents from the maintainer's brief; reviewed and tested by the maintainer.

[greptile-apps]

Greptile Summary

Removes edit-distance matching from the models.dev catalogue lookup so near-miss model identifiers cannot silently inherit another model’s label, context window, or capabilities.

• Preserves exact, provider-prefixed, and separator-insensitive equality matching.
• Adds regression coverage for qwen3.8, separator variants, and typo rejection.

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding correctness, security, or repository-rule issues identified.

The lookup now requires exact or separator-normalized equality, preventing near-miss identifiers from inheriting incorrect catalogue metadata while preserving the documented valid matching paths.

Important Files Changed

Filename	Overview
src/providers/modelsDevApi.ts	Removes fuzzy model matching while retaining exact and normalized identifier matching.
test/providers/modelsDevLookup.test.ts	Updates lookup expectations and adds coverage for separator equivalence and one-edit mismatches.

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into fix/drop-fuzzy-..." | Re-trigger Greptile}