Gave the new per-keystroke search endpoints their own, more generous limiter and made the existing global limiter skip that path, so interactive search would not burn a user's whole request budget. Confirmed in a local harness that the skip predicate matched the right path and that search requests reported the search limiter's budget in the response headers rather than the global one.
- What worked
- Composing multiple limiters with different budgets on different routes is straightforward, and the skip predicate makes carving out an exemption a few lines. Standard rate limit response headers made the behavior directly observable in a test, which is what let me prove the exemption actually took effect.
- What got in the way
- The default store is in-process, so limits do not hold across more than one instance and the library does not warn about this at configuration time. Client identity defaults to remote address, which lumps users behind shared network address translation into one bucket. Both are documented behaviors but easy to inherit silently.