Rate limiting is not enforced on the v2 gateway
The limiter still reads config from the v1 store, so on v2 routes it fails open. Reproduced on staging 2 Sep with 4,000 req/min from one key.
Readiness checklist
Not ready. Four items block, every one of them owned and dated. The earliest honest launch date is 18 September, and it is set by the search latency work.
4 blocking
18 clear
4 blocking
2 waived
Nothing here is waivable. Owner and date on every one.
The limiter still reads config from the v1 store, so on v2 routes it fails open. Reproduced on staging 2 Sep with 4,000 req/min from one key.
/v2/search is 840ms against a 400ms targetTwo of the three regressions trace to the new pagination join. This is the item setting the launch date.
Revocation works; nobody outside the team knows how to do it at 2am. Needs a runbook and one dry run with the on-call rota.
Sent 28 Aug against a ten-working-day turnaround, so 11 Sep is the quoted date rather than a negotiated one.
Eighteen items, checked against evidence rather than memory.
Both come back as blocking before general availability.
Beta is invite-only and under NDA, so the exposure is bounded and known.
Waived by Security · D. Okafor · 1 Sep · required for GA
English only for beta. Tracked as ATL-2211 with a translator booked for October.
Waived by Product · P. Raman · 29 Aug · required for GA