Add integration test for the creator key price history endpoint returning prices in ascending timestamp order

[Chucks1093]

Summary

The key price history endpoint should return historical price snapshots ordered oldest-first so clients can plot a chart without sorting. An integration test should seed snapshots out of order and confirm the response is always chronologically sorted.

Scope

• Seed three price snapshots at T+30m, T+10m, and T+20m (out of order)
• Call the price history endpoint and assert the response order is T+10m, T+20m, T+30m
• Assert each entry includes price, supply, and recorded_at fields
• Assert cursor pagination works correctly across pages of price history
• Assert an unknown creator returns 404

Acceptance Criteria

• Snapshots returned in ascending timestamp order
• Each entry includes price, supply, and recorded_at
• Cursor pagination correct across pages
• Unknown creator returns 404

ETA: 12 hours

---

Coordinate on Telegram

[LumDev86]

Hi — I'd like to take this one.

Express + Prisma + PostgreSQL is my daily stack, and this is the kind of
ordering guarantee that passes by accident: if the seed data happens to go
in already sorted, the test goes green without the endpoint sorting
anything. So I'd seed deliberately out of order as the scope says
(T+30m, T+10m, T+20m) and assert the exact returned sequence, not just
that the result is sorted.

Plan:

• Seed the three snapshots out of order, assert the response comes back
  T+10m, T+20m, T+30m
• Assert every entry carries price, supply and recorded_at
• Cursor pagination: page through with a page size smaller than the seeded
  set, and assert the concatenated pages preserve ascending order with no
  duplicates or gaps across the page boundary — that boundary is where
  cursor pagination usually breaks
• Unknown creator returns 404

Jest against a seeded Postgres using the docker compose setup already in
the repo, run with pnpm test, following the existing integration test
layout.

I saw the 12-hour ETA. Could you assign it to me? Happy to coordinate on
Telegram.

[guptakumarranjeet150]

Hello! I'd like to work on this issue.

I would love to take this on. My planned approach:

• Structure backend handlers for Add integration test for the creator key price history endpoint returning prices in ascending timestamp order with strict input validation, proper HTTP error codes, and idempotent execution.
• Cover implementation with end-to-end integration tests for standard and edge-case inputs.

Happy to pick this up today—please assign to me!