-- Reverses 000015.
--
-- Dropping the counters removes every in-flight rate limit window. The effect
-- is that limits reset once, which is the correct meaning of rolling back a
-- counter table: it destroys no application data, and a caller who was at their
-- limit gets a fresh window rather than a permanent refusal.
--
-- The in-process limiter in httpserver/ratelimit.go is untouched by this
-- migration and by its rollback; login limiting keeps working either way.

SET search_path = public;

DROP TABLE IF EXISTS public.rate_limits;