Problem
src/signals/contributor-pr-outcomes.ts backs GET /v1/contributors/:login/pr-outcomes — a genuinely hosted, multi-tenant-safe, per-GitHub-login data source (public-safe attribution only, no reward/wallet fields) that is exactly the server-side ground truth a hosted miner dashboard's "past attempts (merged)" view needs, since it doesn't depend on any per-tenant local sqlite store. Nothing on the AMS side calls it today.
Area
packages/loopover-miner/.
Proposal
Deliverable is a CLI command specifically — not MCP, not miner-ui (both are separate, already-tracked surfaces; see #7656 and #7675 for the miner-ui/dashboard-side work). Add a real CLI command that calls GET /v1/contributors/:login/pr-outcomes for the current miner's own configured GitHub login and prints the result, mirroring this package's existing CLI command patterns (check packages/loopover-miner/lib/*-cli.js/*-cli.ts for the house shape before starting — flag parsing, output formatting, error handling should all match an existing command, not invent a new CLI convention).
Deliverables
Test Coverage Requirements
packages/loopover-miner/** — match this package's existing CLI test conventions (see any existing *-cli.test.ts for the pattern).
Resources
src/signals/contributor-pr-outcomes.ts, src/api/routes.ts (the existing endpoint)packages/loopover-miner/lib/ — pick an existing *-cli.ts file as the structural template
Boundaries
Merged-PR outcomes only, per the endpoint's current scope (no closed/rejected outcomes, no in-flight attempts) — those are separate, local-only data (see #7656) unless a future issue extends this endpoint itself. CLI only — MCP and dashboard exposure are separate, already-filed issues, not this one's job.
Contributor-eligible. CLI command only, per the Proposal above — a PR that builds an MCP tool or a miner-ui route instead does not satisfy this issue.
Problem
src/signals/contributor-pr-outcomes.tsbacksGET /v1/contributors/:login/pr-outcomes— a genuinely hosted, multi-tenant-safe, per-GitHub-login data source (public-safe attribution only, no reward/wallet fields) that is exactly the server-side ground truth a hosted miner dashboard's "past attempts (merged)" view needs, since it doesn't depend on any per-tenant local sqlite store. Nothing on the AMS side calls it today.Area
packages/loopover-miner/.Proposal
Deliverable is a CLI command specifically — not MCP, not miner-ui (both are separate, already-tracked surfaces; see #7656 and #7675 for the miner-ui/dashboard-side work). Add a real CLI command that calls
GET /v1/contributors/:login/pr-outcomesfor the current miner's own configured GitHub login and prints the result, mirroring this package's existing CLI command patterns (checkpackages/loopover-miner/lib/*-cli.js/*-cli.tsfor the house shape before starting — flag parsing, output formatting, error handling should all match an existing command, not invent a new CLI convention).Deliverables
*-cli.tscommand's exact structure.Test Coverage Requirements
packages/loopover-miner/**— match this package's existing CLI test conventions (see any existing*-cli.test.tsfor the pattern).Resources
src/signals/contributor-pr-outcomes.ts,src/api/routes.ts(the existing endpoint)packages/loopover-miner/lib/— pick an existing*-cli.tsfile as the structural templateBoundaries
Merged-PR outcomes only, per the endpoint's current scope (no closed/rejected outcomes, no in-flight attempts) — those are separate, local-only data (see #7656) unless a future issue extends this endpoint itself. CLI only — MCP and dashboard exposure are separate, already-filed issues, not this one's job.
Contributor-eligible. CLI command only, per the Proposal above — a PR that builds an MCP tool or a miner-ui route instead does not satisfy this issue.