feat(aws-bedrock-mantle/nvidia.nemotron-nano-12b-v2): add new models [bot]

[models-bot]

Auto-generated by model-addition-agent for aws-bedrock-mantle/nvidia.nemotron-nano-12b-v2.

---

Note

Low Risk
Config-only addition of a model definition; no runtime, auth, or data-path changes.

Overview
Adds a new aws-bedrock-mantle provider entry for nvidia.nemotron-nano-12b-v2, registering the model id and listing 14 AWS regions under costs.

The config sets mode: unknown (typical for bot-generated additions until pricing/behavior is filled in). No application logic changes—only this YAML catalog file.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

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

[cursor]

Cost entries lack pricing data but bypass empty-costs filter

Medium Severity

The costs entries contain only region keys with no actual pricing values (input_cost_per_token, output_cost_per_token, etc.). Because the costs array is non-empty (13 items), the model passes the costs.length === 0 filter in build-unified-json.ts and will be emitted into the output JSON. Every other model in the codebase following this sparse pattern (region-only costs, mode: unknown) is explicitly marked isDeprecated: true or status: retired, but this new entry has neither marker. Downstream consumers receiving cost entries with undefined pricing values may produce NaN calculations or incorrect behavior.

 

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