sync-validate

Run this review against src/index.ts to check each sync against a 14-point checklist covering pagination termination, cursor advancement, state handling, and deletion markers. Findings are grouped by severity with concrete code fixes.

Infinite loops happen when nextState never advances or hasMore never becomes false. Skipped records usually come from missing overlap windows during backfill-to-delta transitions or cursors without consistency buffers on eventually consistent APIs.

Use incremental mode when the source API supports change tracking such as updated_at filters or event feeds. Replace mode re-fetches everything each cycle, which wastes requests and can miss deletions handled differently between modes.

Check whether the source API exposes a delete signal such as an audit log or archived filter. If it does, emit delete markers with the record key; if the signal lives on a separate endpoint, alternate streams at cycle boundaries using the flip-flop pattern.

The review is a static checklist-based audit of sync code and does not execute the sync against live APIs. It cannot detect runtime issues like actual rate limiting behavior or API-specific response quirks beyond what is visible in the code.