mirror of
https://github.com/instructkr/claw-code.git
synced 2026-11-16 00:00:40 +08:00
test(api): lock the README model-alias table to the resolver
The `## Model Aliases` table and `MODEL_REGISTRY` had drifted: the table listed only the three Anthropic aliases while the resolver had grown the xAI and Kimi entries, so an alias could resolve without being documented. Assert the two agree in both directions — every registry alias appears in the table with the canonical id and auth env var it actually resolves to, and the table introduces no alias the resolver does not know. Each row is also checked case-insensitively, since the README claims `OPUS` behaves the same as `opus`. Also pin that a provider-prefixed form such as `anthropic/opus` is not an alias: it is passed through as-is rather than expanded. The README now says so, which is what made the distinction worth a test rather than a comment.
This commit is contained in:
1 parent
b89ddda387
commit
072594dfee
2 files changed
+133
-1
No files matched your search
+4
-1
@@ -113,7 +113,10 @@ Primary artifacts:
|
||||
Short model aliases resolve to canonical model IDs. Because the router selects a
|
||||
provider from the resolved model, an alias also determines which backend and
|
||||
credentials are used — choose the alias for the provider you have an API key for.
|
||||
Alias resolution is case-insensitive (`OPUS` behaves the same as `opus`).
|
||||
Alias resolution is case-insensitive (`OPUS` behaves the same as `opus`). Aliases
|
||||
are the bare short names listed below: a prefixed form such as `anthropic/opus`
|
||||
is not an alias, and is passed through as-is rather than expanded to
|
||||
`claude-opus-4-7`.
|
||||
|
||||
| Alias | Resolves To | Provider | Auth env var |
|
||||
|-------|-------------|----------|--------------|
|
||||
|
||||
Reference in new issue
Block a user