Market catalog cursors now stay valid for 8 hours instead of 24
GET /v1/markets cursors stay bound to the immutable catalog snapshot that
issued them. Replaced snapshots now remain available for up to 8 hours instead
of 24. Nothing else about the endpoint changes: same rows, same order, same
filters, same snapshot.observed_at behavior.
Why. Each provider refresh publishes a complete new snapshot and the old ones are kept so in-progress paginations can finish. At the 30-minute catalog interval a 24-hour window keeps ~48 copies of every provider, which set the size of the Valkey instance. Nobody pages a catalog for 8 hours — a full walk of the whole catalog at the slowest rate limit takes under an hour — so the older half of the window was shelf space, not a feature. The shorter window is what lets the instance be right-sized (tracked separately).
What may need changing. If you hold a next_cursor longer than 8 hours
before continuing, it now answers 400 pagination cursor is stale — restart
from the first page. Cursors were already documented as short-lived session
state with no guaranteed grace under storage pressure; treat them that way.