### Summary

A cached key whose role is `PROXY_ADMIN` returns from `user_api_key_auth()` before the normal `blocked` check. A stale local cache entry on another worker can therefore continue to authenticate after the key has been blocked in the database

### Current behavior

After loading a cached `UserAPIKeyAuth`, the proxy has a privileged early return for proxy-admin keys. That path checks expiration and updates request context, but it does not check `valid_token.blocked`

The ordinary non-admin path checks `valid_token.blocked` later

`block_key()` updates the database and attempts to delete the key from the local cache and the shared cache. The invalidation is not guaranteed to synchronously remove a stale entry from every worker. A worker that still serves the old cached admin object reaches the privileged early return and never consults the database

### Reproduction

Use two proxy workers with a shared database and cache:

1. Authenticate an admin key through worker B so its local cache contains `blocked=False` 2. Block the key through the management API or directly in the database 3. Make another request with the same key through worker B before its local cache refreshes …