feat(aws-bedrock-mantle/zai.glm-4.7): add new models [bot]

[models-bot]

Auto-generated by model-addition-agent for aws-bedrock-mantle/zai.glm-4.7.

---

Note

Low Risk
Single new provider YAML with no code or auth changes; only extends the model catalog.

Overview
Adds a new aws-bedrock-mantle provider entry for zai.glm-4.7, registering the model with mode: unknown and a costs list covering eleven AWS regions (US, EU, SA, and APAC).

This is an auto-generated catalog/config file only; no application or routing logic is changed in this diff.

^{Reviewed by Cursor Bugbot for commit 07d6b76. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 07d6b76. Configure here.}

[cursor]

Cost entries missing pricing data for all regions

High Severity

Each entry in the costs list only contains a region key without input_cost_per_token or output_cost_per_token. Every other active model in the repository (e.g., providers/aws-bedrock/zai.glm-4.7.yaml) includes both cost fields per region. This renders the pricing information completely non-functional — consumers of this data will find no cost values for any region.

 

^{Reviewed by Cursor Bugbot for commit 07d6b76. Configure here.}

[cursor]

Model mode incorrectly set to unknown for active model

Medium Severity

The mode is set to unknown, but the corresponding model in providers/aws-bedrock/zai.glm-4.7.yaml uses mode: chat. In this repository, mode: unknown is only used for deprecated/retired models that also carry isDeprecated: true. Since this is a new active model, using unknown may cause routing or capability detection failures.

 

^{Reviewed by Cursor Bugbot for commit 07d6b76. Configure here.}