### Check for existing issues

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

### What happened?

Budget enforcement for end users reads a cross-pod Redis counter, `spend:end_user:{user_id}`. When that counter is missing (default TTL is 60s, `BaseCache.default_ttl`), `SpendCounterReseed.from_db()` is supposed to reseed it from the persisted spend in `LiteLLM_EndUserTable` before enforcement runs, the same way it already does for key, team, team-member, user, and org counters. The end-user branch currently returns `None` unconditionally instead of querying the database: ```python elif counter_key.startswith("spend:end_user:"): return None ``` Because of this, enforcement falls back to `fallback_spend`, a per-pod cached value (`end_user_id:{user_id}.spend` in `user_api_key_cache`) governed by `general_settings.user_api_key_cache_ttl`. Each pod refreshes this cache independently, so at the moment the Redis counter disappears, whichever pod handles the next request may reconstruct it using a value that is lower than both the database and other pods' state.

### Steps to Reproduce

1. In a multi-pod deployment, create an end user with …