feat(mcp): add loopover_get_repo_settings mirroring GET /repos/:owner/:repo/settings

[bitfathers94]

feat(mcp): add loopover_get_repo_settings mirroring GET /repos/:owner/:repo/settings

Expose the raw effective maintainer settings row (resolveRepositorySettings) over
MCP, the last unmirrored read in the settings / automation-state / gate-config-effective
trio. Mirrors loopover_get_automation_state: same ownerRepoShape input, same
maintainer-only repo-access boundary, thin GET proxy returning the resolver output
unmodified. Categorized maintainer; no OpenAPI/schema regen needed.

Closes #9297

Validation

Verified locally on this branch before opening:

• npm run typecheck
• npx turbo run build:tsc build:verify
• npm run test:coverage — patch coverage 100.0% of changed lines

[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 75.81%. Comparing base (c2ac612) to head (3b31d0e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9354      +/-   ##
==========================================
+ Coverage   75.38%   75.81%   +0.43%     
==========================================
  Files         275      276       +1     
  Lines       58023    59218    +1195     
  Branches     6181     6417     +236     
==========================================
+ Hits        43739    44899    +1160     
- Misses      14014    14027      +13     
- Partials      270      292      +22     

Flag	Coverage Δ
backend	97.07% <100.00%> (?)

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

Files with missing lines	Coverage Δ
src/mcp/server.ts	97.07% <100.00%> (ø)

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-27 14:00:18 UTC}

2 files · 1 AI reviewer · no blockers · readiness 95/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
Adds a thin, maintainer-gated MCP tool that proxies resolveRepositorySettings, mirroring the existing loopover_get_automation_state pattern exactly: same requireRepoAccess boundary, same ownerRepoShape input, unmodified spread of resolver output. The regression test asserting byte-identical output to the REST route's resolveRepositorySettings call is a solid, non-fabricated check on the actual invariant the PR claims (no drift between the two surfaces). This is a narrow, well-targeted addition closing the stated issue #9297 with 100% patch coverage on the new code paths (success, byte-identity, and access-denial).

Nits — 2 non-blocking

• src/mcp/server.ts: repoSettingsOutputSchema only declares 5 fields (repoFullName, commentMode, gatePack, reviewCheckMode, slopGateMode) while the tool description promises label/surface/command-auth settings and agent autonomy controls — since it's non-strict/optional this doesn't break anything, but the schema is a weak contract for MCP clients relying on it for shape discovery.
• Consider expanding repoSettingsOutputSchema to list the additional fields (labels, autonomy, etc.) called out in the tool description, or drop those specifics from the description if the schema intentionally stays minimal for now.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#9297
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low 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: 65 registered-repo PR(s), 45 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	bitfathers94; Gittensor profile; 65 PR(s), 0 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Linked issue satisfaction

Partially addressed
The PR adds loopover_get_repo_settings backed by resolveRepositorySettings, registers it under the maintainer category, and includes tests, closely mirroring the requested structure, but the auth check used is requireRepoAccess (an allowlist-based check) rather than a maintainer-specific boundary, and the accompanying test only exercises the allowlist-deny path rather than the 'authorized maintain

Review context

• Author: bitfathers94
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: TypeScript
• Official Gittensor activity: 65 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Triage stale or unlinked PRs.

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://loopover.ai/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.