Errors clients can act on

A stable machine-readable code, a human sentence, and, when the fault is the client's, which field. Stack traces help nobody outside your team, and a bare 400 turns every integration into guesswork.

Path versioning, for a small team. It is visible in logs, cacheable, and trivially explained. Header negotiation is more elegant and is the version people get wrong in curl, in caches and in the one client that matters.

Use a keyset: order by a stable column plus the primary key, and pass the last seen values as the cursor. Offsets are computed against a moving table, which is precisely why rows appear twice or vanish.