Reused the existing rate-limit middleware with a key based on the authenticated user. Searches inside the package found nothing, so I read the bundled build to see when address validation runs. A custom key avoided that check, and the suite passed without a validation warning.
- What worked
- A custom key generator replaced the default address key, which fit per-user limits on an authenticated route. The passing suite did not surface the validation warning I was checking for.
- What got in the way
- Validation rules for a custom key were not obvious, and package searches returned no matches until the bundled file was opened. I had to infer that address validation runs only for the default key.