Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 require-ready-label-and-ci

Greptile Summary

This PR extends the generated sync layer to recognize next_token as a first-class cursor token (both as a request parameter and a response field), and propagates the OpenAPI format hint for since-type parameters so that date-only endpoints receive YYYY-MM-DD values instead of RFC3339 timestamps.

• next_token cursor support: detectPagination in the parser now classifies next_token/nextToken as a cursor request param; nextFieldCursorNames and pageEnvelopeMetadataKeys are updated to recognize the matching response field, keeping detection and runtime extraction consistent.
• Date-format-aware since params: A new SinceParamFormat field is threaded from metaFromEndpoint → syncableMeta → SyncableResource/DependentResource → the generated syncResourceSinceParamFormat switch and formatSyncSinceValue helper, which correctly converts RFC3339 and RFC3339Nano timestamps to YYYY-MM-DD for format: date parameters.
• Expanded since-param heuristics: isEndpointSinceParamName adds exact-match names (start_date, start_datetime, start_time, from_date, from_datetime) to capture common temporal-filter patterns not previously covered by the substring checks.

Confidence Score: 5/5

Safe to merge. The changes are well-scoped additive extensions with no behavioral regressions on existing sync paths.

All three change areas (next_token cursor detection, SinceParamFormat propagation, and date-format conversion) are self-contained and well-tested. The parse ladder in formatSyncSinceValue handles RFC3339, RFC3339Nano, and pure-date inputs correctly. The SinceParamFormat field is threaded consistently through every copy site in profiler.go and both template loops. The injected end-to-end test compiles and exercises the generated code against a realistic multi-leaf spec.

No files require special attention.

Important Files Changed

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[syncResource / syncDependentResource\ncalled with resource name + effectiveSince] --> B{effectiveSince\nnon-empty?}
    B -- No --> E[Skip format step]
    B -- Yes --> C[syncResourceSinceParamFormat\nresource]
    C --> D{SinceParamFormat\ngenerated switch}
    D -- date --> F[formatSyncSinceValue\nvalue, 'date']
    D -- date-time or empty --> G[return value unchanged]
    F --> H{try time.Parse\nRFC3339}
    H -- ok --> I[Format as\n2006-01-02]
    H -- err --> J{try time.Parse\nRFC3339Nano}
    J -- ok --> I
    J -- err --> K{try time.Parse\n2006-01-02}
    K -- ok --> L[return original\nalready a date]
    K -- err --> M[return original\nunparseable fallback]
    I --> N[effectiveSince = YYYY-MM-DD\nsent to API]
    G --> O[effectiveSince = RFC3339\nsent to API]
    L --> N
    M --> O

    style N fill:#d4edda
    style O fill:#d4edda

_{Reviews (2): Last reviewed commit: "fix(cli): address sync resource review f..." | Re-trigger Greptile}

Merge Queue Status

• ✅ Entered queue — 2026-06-07 22:45 UTC · Rule: default
• ✅ Checks passed · on draft merge queue: embarking main (88617bb) and #2818 together #2846
• ✅ Merged — 2026-06-07 22:56 UTC · at a0a3b65088e0e45d2a038eb6b201ef7d2da6f410 · squash

This pull request spent 10 minutes 35 seconds in the queue, including 10 minutes 21 seconds running CI.