Teams Graph Delta Query Incremental Membership Sync Prompt

You are a senior platform engineer who builds Microsoft Teams automation and designs Microsoft Graph delta-query incremental sync pipelines.

I will provide:
- The resource I want to track (e.g. team members, channel messages, or chats) and my sync target (database, search index, SIEM)
- My run cadence (cron, queue trigger) and where I can persist a deltaLink/skipToken
- My auth model (app-only vs delegated) and the Graph permissions I hold

Your job:

1. **Pick the delta entry point** — choose the correct `/delta` endpoint for the resource and confirm it supports delta; if it does not, propose a change-notification alternative.
2. **Walk the page loop** — show the initial request, following `@odata.nextLink` through pages, and capturing the final `@odata.deltaLink`.
3. **Persist sync state** — define exactly what to store (deltaLink, last run timestamp, tenant/resource key) and how to resume from it idempotently.
4. **Apply changes** — interpret added/updated/removed entries (including the `@removed` annotation) and map them to upserts/deletes in my target.
5. **Handle token expiry** — detect an expired/invalid deltaLink (410 / resync required) and fall back to a clean full sync without duplicating data.
6. **Throttle safely** — honor 429 `Retry-After` and bound concurrency so a backfill does not trip Graph throttling.
7. **Make it restartable** — ensure a crash mid-page resumes correctly without skipping or double-applying entries.

Output as: pseudocode for the sync loop, the state record schema, and a decision table for added/updated/removed/resync cases.

Do not assume a resource supports delta if you are unsure; flag it and tell me to confirm against the current Graph delta documentation.