Files
Trevin Chow 0f3a8bd053 fix(ce-resolve-pr-feedback): paginate GraphQL connections
On long-lived PRs that accumulated more than one page of review threads,
the skill silently dropped everything past page 1 of each GraphQL
connection and reported "0 of 0 resolved" while real findings sat
unanswered.

The two GraphQL fetch scripts now paginate. `gh api graphql --paginate`
follows only one `pageInfo` per response, so `get-pr-comments` issues
three separate paginated queries (reviewThreads, comments, reviews) and
assembles the result before running the existing filter; the inline
per-thread comment cap is also bumped from 10 to 100 (without
follow-up pagination — threads exceeding that depth are rare and out
of scope here). `get-thread-for-comment` paginates reviewThreads the
same way.

A new tests/resolve-pr-feedback-pagination.test.ts enforces the
contract: each top-level connection is paginated with `after:
$endCursor` and selects `pageInfo { hasNextPage endCursor }`.

Fixes #798.
2026-05-08 15:14:06 -07:00
..
2026-04-22 14:21:19 -07:00