feat(miner): expose the calibration report as a read-only MCP tool - #5909
Merged
JSONbored merged 1 commit intoJul 15, 2026
Merged
Conversation
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
marked this pull request as draft
July 14, 2026 22:27
Contributor
|
Warning LoopOver found maintainer review notesScoped related-work signals were found for this PR. They are advisory unless the gate reports a blocker. Readiness score: 57/100
Signal definitions
Review context
Maintainer notes
Contributor next steps
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers. |
This was referenced Jul 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5909 +/- ##
=======================================
Coverage 95.15% 95.15%
=======================================
Files 589 589
Lines 46695 46695
Branches 14902 14902
=======================================
Hits 44434 44434
Misses 1511 1511
Partials 750 750
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Add loopover_miner_get_calibration_report to the miner's stdio MCP server, wrapping the existing local prediction-ledger/event-ledger join (calibration-cli.js's toPredictionRecords/toOutcomeRecords + calibration.js's buildCalibrationReport) that already powers `loopover-miner calibration --json`. No new join/scoring logic; an MCP client can now ask for this miner's own merge/close prediction accuracy without shelling out to the CLI. Follows the same injection-seam and store-ownership pattern as the sibling loopover_miner_get_governor_decisions tool. Closes JSONbored#5821
oktofeesh1
force-pushed
the
feat/miner-calibration-report-mcp-tool-5821
branch
from
July 15, 2026 02:13
0c71cea to
9abd466
Compare
JSONbored
marked this pull request as ready for review
July 15, 2026 04:27
JSONbored
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
loopover_miner_get_calibration_reportto the miner's stdio MCP server (packages/loopover-miner/bin/loopover-miner-mcp.js), wrapping the existing local prediction-ledger/event-ledger join that already powersloopover-miner calibration --json. No new join/scoring logic — an MCP client can now ask for this miner's own merge/close prediction accuracy without shelling out to the CLI.Scope
type(scope): short summaryConventional Commit format, for examplefix(api): restore profile access checks.CONTRIBUTING.mdand does not reintroduce GitHub Pages, VitePress,site/, orCNAME.Closes #123) — a linked open issue is required for every contributor PR.Validation
git diff --checknpm run actionlintnpm run typechecknpm run test:coveragelocally;codecov/patchrequires ≥99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.npm run test:workersnpm run build:mcpnpm run test:mcp-packnpm run ui:openapi:checknpm run ui:lintnpm run ui:typechecknpm run ui:buildnpm audit --audit-level=moderateRan the full local gate via
npm run test:ci— green, plusnpm audit --audit-level=moderate(0 vulnerabilities). Note:packages/loopover-miner/bin/**is not in the Codecov coverageincludeglob (onlypackages/loopover-miner/lib/**is), so this file carries no strict patch-coverage obligation — tests were still written to full parity with the siblingloopover_miner_get_governor_decisionstool's coverage (has-signal branch, no-signal branch, store-ownership invariant), plus a new row in the sharedminer-mcp-contract.test.tsinvariant table.Safety
UI Evidencesection below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.If any required check was skipped, explain why:
UI Evidence
Not applicable — no visible UI/frontend/docs/extension change beyond the README's MCP tool list, which is covered by the existing
miner MCP tool documentation paritytest.Notes
options.initPredictionLedger/options.initEventLedger) and explicit store-ownershipfinallypattern as the siblingloopover_miner_get_governor_decisionstool.Closes #5821