Skip to content

REST + CLI mirror for loopover_pr_outcome #6747

Description

@JSONbored

Context

The MCP tool loopover_pr_outcome (src/mcp/server.ts:2155, via prOutcomes at src/mcp/server.ts:3784-3792) returns a contributor's own merged-PR outcome history, self-scoped via requireContributorAccess. No REST route exists (pr-outcome/pr_outcome greps return nothing in src/api/routes.ts) despite fitting the existing /v1/contributors/:login/... route family.

Requirements

  • Add GET /v1/contributors/:login/pr-outcomes[?limit=N] in src/api/routes.ts with requireContributorAccess, reusing listNotificationDeliveriesForRecipient.
  • Add CLI stdio tool/subcommand.

Deliverables

  • GET /v1/contributors/:login/pr-outcomes route
  • CLI stdio tool
  • Unit test

Test Coverage Requirements

99%+ Codecov patch coverage on every changed line and branch in the new route/tool/CLI code, plus a test asserting output parity between the mirrored surfaces for identical input.

Expected Outcome

A contributor's PR outcome history is readable over REST/CLI, not just MCP.

Links & Resources

Precedent: app.get("/v1/contributors/:login/open-pr-monitor", ...) at src/api/routes.ts:3117 — same contributor route family, same auth helper.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions