feat(mcp): register 4 maintainer/repo-owner intake tools in packages/loopover-mcp

[jaytbarimbao-collab]

Summary

The maintainer-triage and repo-owner-intake profiles in packages/loopover-mcp/bin/loopover-mcp.js recommend four tools that were never registered as local stdio tools, so both profiles advertised tools the local server could not serve:

• loopover_get_skipped_pr_audit → GET /v1/app/skipped-pr-audit
• loopover_get_issue_quality → GET /v1/repos/:owner/:repo/issue-quality
• loopover_get_registration_readiness → GET /v1/repos/:owner/:repo/registration-readiness
• loopover_get_config_recommendation → GET /v1/repos/:owner/:repo/gittensor-config-recommendation

Each is now registered as a stdio proxy mirroring its src/mcp/server.ts counterpart's input schema and REST call, reusing the existing apiGet/auth conventions. A descriptor entry is added per tool, plus a skippedPrAuditShape for the audit filters. The remote server is unchanged. The #4777 stdio-tool-count invariant is updated 37 → 41 for the four newly-registered tools.

Tests

New test/unit/mcp-cli-intake-tools.test.ts covers each tool with a success path (proxies to the right endpoint, returns the payload, no private-surface leakage) and an API-failure path (surfaces as a tool error); fixture handlers added to the shared harness. Full mcp-cli suite + mcp-tool-rename-aliases + tsc green.

Closes #6151

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.33%. Comparing base (4a5bd94) to head (79e0950).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6199   +/-   ##
=======================================
  Coverage   95.33%   95.33%           
=======================================
  Files         599      599           
  Lines       47186    47186           
  Branches    15032    15032           
=======================================
  Hits        44983    44983           
  Misses       1477     1477           
  Partials      726      726           

Flag	Coverage Δ
shard-1	43.94% <ø> (ø)
shard-2	36.66% <ø> (ø)
shard-3	32.17% <ø> (+0.06%)	⬆️
shard-4	34.13% <ø> (+0.13%)	⬆️
shard-5	32.21% <ø> (+0.72%)	⬆️
shard-6	44.89% <ø> (-0.31%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-15 21:21:17 UTC}

4 files · 1 AI reviewer · no blockers · readiness 82/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR registers four previously-missing stdio proxy tools (loopover_get_issue_quality, loopover_get_registration_readiness, loopover_get_config_recommendation, loopover_get_skipped_pr_audit) in packages/loopover-mcp/bin/loopover-mcp.js, mirroring the existing apiGet/registerStdioTool/ownerRepoShape conventions used elsewhere in the file. Each proxy is correctly wired to its documented REST endpoint with proper encodeURIComponent usage and query-param handling for the audit filters, and the #4777 invariant test is updated 37→41 with matching new coverage in mcp-cli-intake-tools.test.ts (success path, API-failure path, and no-leak assertions). The change is narrowly scoped, closes #6151 as stated, and the diff is internally consistent with its description.

Nits — 3 non-blocking

• packages/loopover-mcp/bin/loopover-mcp.js: the four new registerStdioTool calls duplicate the `${prefix}/...` pattern already used by loopover_feasibility_gate and others — consider a small helper if a fifth owner/repo-scoped proxy is added later.
• test/unit/mcp-cli-intake-tools.test.ts: the FORBIDDEN_PUBLIC_TERMS regex is fairly narrow (specific phrasing) — a future payload shape change could leak private fields without tripping it.
• packages/loopover-mcp/bin/loopover-mcp.js:654-706: consider extracting a tiny `ownerRepoProxy(name, endpoint, resultLabel)` factory to cut the repetition across the three ownerRepoShape-based tools, purely optional given only three instances exist.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#6151
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 118 registered-repo PR(s), 59 merged, 4 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jaytbarimbao-collab; Gittensor profile; 118 PR(s), 4 issue(s).
Gate result	✅ Passing	No configured blocker found.
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Linked issue satisfaction

Addressed
The PR registers all four tools (loopover_get_issue_quality, loopover_get_registration_readiness, loopover_get_config_recommendation, loopover_get_skipped_pr_audit) as stdio proxies mirroring the remote server's endpoints, using the existing apiGet/auth conventions and adding descriptors, and updates the related tool-count invariant test. It also adds a dedicated test file covering success and fai

Review context

• Author: jaytbarimbao-collab
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 118 PR(s), 4 issue(s).
• Related work: Items reference the same linked issue feat(mcp): register 4 maintainer/repo-owner intake tools in packages/loopover-mcp (get_skipped_pr_audit/get_issue_quality/get_registration_readiness/get_config_recommendation) #6151. (issue #6151)
• Related work: Open PR work references issue feat(mcp): register 4 maintainer/repo-owner intake tools in packages/loopover-mcp (get_skipped_pr_audit/get_issue_quality/get_registration_readiness/get_config_recommendation) #6151. (issue #6151)
• Related work: Titles/paths share 6 meaningful terms. (issue #6150)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Start here: Review top overlaps.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://gittensory.aethereal.dev/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 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.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.