Implement P2 GitHub pagination + claim status mapping regressions

[revsmoke]

Summary

• fall back to paginated REST issue listing when gh issue list hits the 200-item cap
• paginate REST issue comments in issue-detail fallback path until all comments are retrieved
• add HTTP regression coverage for invalid_transition -> 409 on claim mutation routes
• update QA risk register statuses for IC-QA-003/004/005/006 and release recommendation

Validation

• bun run typecheck
• bun test
• bun test tests/github.test.ts
• bun test tests/http-server.integration.test.ts

Summary by CodeRabbit

• New Features

  • Added automatic fallback mechanism for handling large GitHub issue lists.
  • Improved pagination for comprehensive issue comment retrieval.

• Bug Fixes

  • Enhanced claim status transition validation to properly reject invalid state changes.

• Tests

  • Expanded test coverage for API fallback scenarios and paginated data fetching.
  • Added validation tests for claim status transition enforcement.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

QA risk register updated with resolved findings and GO release decision. GitHub integration enhanced with API fallback mechanism and pagination for handling large issue and comment datasets. Test coverage expanded for both GitHub service fallback scenarios and HTTP server status transition validation.

Changes

Cohort / File(s)	Summary
QA Documentation QA_RISK_REGISTER_2026-02-09.md	Status updates for IC-QA-001 through IC-QA-006 findings marked as resolved with remediation metadata. Release decision changed from NO-GO to GO, reflecting validation of P0/P1 findings through typecheck and tests.
GitHub Integration src/github.ts	Introduced GH_ISSUE_LIST_LIMIT (200) and REST_PAGE_SIZE (100) constants. listOpenIssues now falls back to REST API when GitHub CLI results reach the limit. getIssueDetailsViaRest refactored to paginate comment fetching beyond first 100 items using REST_PAGE_SIZE.
GitHub Service Tests tests/github.test.ts	Added test coverage for REST fallback when gh reaches result limit and for pagination of issue comments beyond 100. Both scenarios verify correct API selection, filtering, and complete data aggregation.
HTTP Server Integration Tests tests/http-server.integration.test.ts	Extended claim mutation test with assertion for invalid status transition, verifying HTTP 409 response with reason: invalid_transition after successful ownership initialization.

Sequence Diagram

sequenceDiagram
    participant Client as GitHub Service
    participant GhCLI as GitHub CLI
    participant REST as REST API
    
    rect rgba(100, 150, 200, 0.5)
        Note over Client,REST: listOpenIssues with Fallback
        Client->>GhCLI: List open issues (limit: 200)
        GhCLI-->>Client: Returns 200 items
        
        alt Results hit limit
            Client->>Client: Detect result count >= GH_ISSUE_LIST_LIMIT
            Client->>Client: Log fallback warning
            Client->>REST: Fetch via REST API (pagination)
            loop For each page
                REST-->>Client: Page of issues (per_page: 100)
            end
            Client-->>Client: Aggregate all pages
        else Results below limit
            Client-->>Client: Return gh results
        end
    end
    
    rect rgba(150, 200, 100, 0.5)
        Note over Client,REST: getIssueDetailsViaRest with Comment Pagination
        Client->>REST: Fetch issue details + comments (page 1)
        REST-->>Client: Issue + first 100 comments
        
        loop While more pages exist
            Client->>REST: Fetch next page of comments
            REST-->>Client: Additional comments (per_page: 100)
        end
        Client-->>Client: Aggregate all comments
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~30 minutes

Poem

🐰 Our issues now scale with grace so grand,
When GitHub's API reaches its land,
We pivot to REST with pagination's might,
QA findings resolved, the release burns bright! 🚀
From NO-GO to GO, the path is now clear!

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/p2-github-pagination-and-contract-tests

---

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