fix(github): report the raw page length from list_repository_issues

[bakey]

Fixes #229.

list_repository_issues fetches one GitHub page and filters pull requests out of it, which destroys the only pagination signal page-number callers have: the filtered array's length says nothing about the raw page length. A short page may be a full page with PRs mixed in, and an empty page may be 100 consecutive PRs — so any paginating consumer that stops on a short or empty page silently drops every later issue, and no sound termination rule can be built from the filtered response alone (details in #229).

The response now carries pageInfo.fetched — the number of items GitHub returned before filtering — declared in the output schema and in the action description: callers must continue paginating while fetched equals the requested page size, even when issues comes back short or empty. The PR-filtering behavior itself is unchanged.

Tests cover the mixed page (fetched=3, filtered ids [1,3]), the all-pull-requests page (fetched=2, issues=[] — the case that defeats every downstream heuristic), and the schema declaration. npm run typecheck, oxfmt, and the full vitest suite (557 tests) pass.

[coderabbitai]

Summary by CodeRabbit

• Enhancements
  • GitHub issue listings now include pageInfo.fetched, indicating how many items were fetched from the current GitHub page—even when pull requests are filtered out and the returned issues list is empty.
  • If perPage isn’t provided, the listing uses GitHub’s default page size (30) and applies the defined perPage limits.
• Tests
  • Expanded coverage to validate filtering behavior, pagination metadata (pageInfo.fetched), and the updated request/response contract.

Walkthrough

The GitHub list_repository_issues action now documents pagination behavior when pull requests are filtered out and returns a required pageInfo.fetched integer alongside the filtered issues. Runtime behavior defaults perPage to 30, sends it to GitHub, and reports the raw page length. Tests cover mixed pages, all-pull-request pages, the default page size, and schema validation.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows the required type(scope): subject format and accurately summarizes the GitHub pagination fix.
Description check	✅ Passed	The description clearly explains the pagination-signal bug and the pageInfo.fetched fix in the PR.
Linked Issues check	✅ Passed	The changes implement #229 by adding pageInfo.fetched, updating the schema and description, and preserving PR filtering.
Out of Scope Changes check	✅ Passed	The added tests and schema/runtime updates stay focused on the reported pagination fix.

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

src/providers/github/runtime-issue.test.ts (1)

70-80: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Assert that pageInfo is required at the top level.

This test verifies that fetched is required inside pageInfo, but not that outputSchema.required contains "pageInfo". Add that assertion to protect the complete output contract from future regression.

Suggested assertion

     const pageInfoProperties = pageInfo?.properties as Record<string, JsonSchema> | undefined;
+    const outputRequired = action?.outputSchema.required as string[] | undefined;

     expect(perPage).toMatchObject({ type: "integer", minimum: 1, maximum: 100, default: 30 });
     expect(pageInfoProperties?.fetched?.type).toBe("integer");
     expect(pageInfo?.required as string[] | undefined).toContain("fetched");
+    expect(outputRequired).toContain("pageInfo");

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/providers/github/runtime-issue.test.ts` around lines 70 - 80, Extend the
“declares the pagination contract in the action schemas” test to inspect the
action output schema’s top-level required fields and assert that it contains
“pageInfo”. Keep the existing nested fetched requirement and other pagination
assertions unchanged.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/providers/github/runtime-issue.test.ts`:
- Around line 70-80: Extend the “declares the pagination contract in the action
schemas” test to inspect the action output schema’s top-level required fields
and assert that it contains “pageInfo”. Keep the existing nested fetched
requirement and other pagination assertions unchanged.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a19b626f-c764-48f3-888f-098d9307fb2d

📥 Commits

Reviewing files that changed from the base of the PR and between 3d9f527 and 491a355.

📒 Files selected for processing (3)

• src/providers/github/actions.ts
• src/providers/github/runtime-issue.test.ts
• src/providers/github/runtime-issue.ts