[models-bot]

This PR adds a new model 123/456 to the catalog.

Submitted via the TrueFoundry Model Catalog UI.

---

Note

Low Risk
Catalog-only addition of one YAML file with no runtime or auth changes; risk is mainly invalid or incomplete catalog metadata.

Overview
Adds a new model catalog entry for 123/456 by introducing providers/123/456.yaml, registering the model under provider 123 in the TrueFoundry catalog (community submission from the Model Catalog UI).

The new file currently contains only the placeholder content x, unlike typical model YAMLs that define metadata such as costs, limits, and mode—reviewers may want to confirm the file matches the expected schema before merge.

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

[github-actions]

SDK live feature checks

Result: skipped — no models to test.

Informational — does not block merge.

[cursor]

Cursor Bugbot has reviewed your changes using default effort 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 d460244. Configure here.}

[cursor]

Invalid model catalog YAML

High Severity

The new catalog file contains only x and omits the required model and mode fields, so CUE validation fails and 123/456 is not added to the catalog.

 

^{Triggered by learned rule: Don't flag model-addition-agent stubs as incomplete}

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

[cursor]

Unsupported provider directory added

Medium Severity

123 is not a gateway-integrated provider. A new providers/123 tree cannot be routed and would appear in the generated Supported Providers table as if the gateway supported it.

 

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

[caiotheodoro]

closing, test probe (placeholder yaml, not a real model)