-
-
Notifications
You must be signed in to change notification settings - Fork 90
CLI mirror for loopover_get_outcome_calibration #6735
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Context
The MCP tool
loopover_get_outcome_calibration(src/mcp/server.ts:1926) mirrorsGET /v1/repos/:owner/:repo/outcome-calibration(src/api/routes.ts:2709, maintainer-gated viarequireRepoMaintainer, supports?windowDays=). No CLI mirror exists even though the sibling gate-telemetry report (maintain precision) already has one.Requirements
maintain outcome-calibration [--window-days N]subcommand tomaintainCli, GETting{repoBase}/outcome-calibration?windowDays=.printMaintainHelp.Deliverables
maintain outcome-calibrationsubcommandprintMaintainHelpTest 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
Maintainers can pull outcome-calibration reports from the CLI, matching the existing
maintain precisionpattern.Links & Resources
Precedent:
maintain precisionatloopover-mcp.js:2779-2798(identical--window-daysquery param handling).