## What happened?

After successfully setting `model_aliases` on a team via `POST /team/update`, the `GET /team/info` endpoint returns `litellm_model_table: null`, making it impossible to read back the configured model aliases.

The aliases **do work** for routing — requests using the alias are correctly forwarded to the target model. The issue is only with the `/team/info` read-back.

## Steps to reproduce

1. Update model aliases on a team:

```bash curl -s https://<PROXY_URL>/team/update \ -H "Authorization: Bearer sk-<MASTER_KEY>" \ -H "Content-Type: application/json" \ -d '{ "team_id": "<TEAM_ID>", "litellm_model_aliases": {"my-alias": "gpt-4o"} }' ```

2. ✅ Update response correctly includes the aliases:

``` { "data": { "litellm_model_table": { "model_aliases": { "my-alias": "gpt-4o" } } } } ``` 3. Query team info: ``` curl -s "https://<PROXY_URL>/team/info?team_id=<TEAM_ID>" \ -H "Authorization: Bearer sk-<MASTER_KEY>" ``` 4. ❌ `litellm_model_table` is null: ``` { "team_info": { "team_alias": "my-team", "litellm_model_table": null } } ``` ## Expected behavior

GET /team/info should ret…