API Cursor Loop Prevention

Keeping the Final Cursor Page and Stopping Infinite Loops

Independent demonstration — not client work (July 2026)

A small iterator keeps terminal-page records and fails clearly if an API repeats a cursor instead of spinning forever.

Problem Cursor integrations sometimes inspect next_cursor before consuming the page they just received. The final page vanishes silently. A repeated non-terminal cursor can also trap a job in an infinite loop.

Approach I moved item delivery ahead of the terminal decision and tracked request cursors at the smallest useful boundary. The code remains generic and has no HTTP-client dependency.

Proof Three tests retain the terminal record, accept an empty terminal page, and detect a repeated cursor. Verification confirms three deterministic standard-library tests passed.