### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

I would like LiteLLM to provide reconciliation and repair tools for team membership and team/user budget relationships.

Suggested behavior:

1. Admin API can scan for inconsistent team membership records. 2. Admin API can repair missing or stale relationships. 3. Budget/member relationships can be validated after team updates. 4. Admin UI can show warnings when inconsistent data is detected. 5. Reconciliation actions are auditable.

Example use cases:

- a user appears in a team list but does not have the expected membership relation - a team member budget record is missing or stale - a deleted/recreated user leaves orphaned membership state - migration or upgrade creates inconsistent team/member records

### Motivation, pitch

Enterprise LiteLLM deployments often have many teams, users, budgets, and virtual keys. Over time, data can become inconsistent because of migrations, partial failures, manual database changes, or older versions of the product.

When team membership or budget state is inconsistent, admins need safe tools to detect and repa…