fix(docs): rename stale gittensory reference in miner MCP client-config doc

[JSONbored]

Summary

• test/unit/miner-mcp-client-config-doc.test.ts was failing on main's full test:ci gate: it asserted packages/loopover-miner/README.md still contains ../gittensory-mcp/README.md#client-config, but docs: fix post-rebrand dead gittensory-* references in contributor docs #5884 already renamed that relative link to ../loopover-mcp/.
• The same README's Client config JSON example still used "gittensory" as the ORB server key while its sibling entry was already "loopover-miner" — completed that rename (JSON key + two prose backtick references) and updated the test's matching assertion.

Test plan

• npx vitest run test/unit/miner-mcp-client-config-doc.test.ts — 3/3 pass
• Full npm run test:ci gate green locally

[superagent-security]

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

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-15 00:44:36 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This PR renames a stale "gittensory" mcpServers key and cross-reference link to "loopover"/"loopover-mcp" in packages/loopover-miner/README.md, keeping the test assertions in test/unit/miner-mcp-client-config-doc.test.ts in sync with the doc content. The change is a narrow, mechanical rename that follows through consistently across the JSON key, the two prose backtick references, and the cross-reference path, and matches the stated intent of fixing a test broken by a prior rename in #5884. This is a small, low-risk docs/test-only change with no logic touched.

Nits — 2 non-blocking

• The PR description doesn't explicitly link to a maintainer-authorized issue beyond referencing docs: fix post-rebrand dead gittensory-* references in contributor docs #5884 and Add an example MCP client config snippet for running AMS's MCP tools alongside gittensory-mcp #5163 in code comments — worth confirming this rename is tracked or considered self-evident maintenance given it's a same-day follow-up to a merged PR.
• Consider grepping the rest of the repo (e.g. docs site content referenced in gittensory.aethereal.dev sources, if present in this repo) for any other stale "gittensory" mcpServers key references missed by this narrow fix.

Concerns raised — review before merging

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

2. Maintainer requires a linked issue — Link the relevant issue (for example `Closes #123`) before opening the PR.

Signal	Result	Evidence
Code review	❌ 2 blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
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 (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 43 registered-repo PR(s), 35 merged, 373 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 43 PR(s), 373 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	⚠️ ℹ️ Insufficient signal	risk: clean · value: insufficient-signal — Nothing measurable for the structural-improvement analyzers on this PR (e.g. no code files changed). LLM value judgment: minor — This is a small, well-targeted consistency fix that repairs a test broken by a prior rename, with no functional code impact.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 43 PR(s), 373 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• No action.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

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.

[BETA] Chat with Gittensory

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

• @gittensory ask <question> answers contribution-quality Q&A with source citations and freshness.
• @gittensory chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @gittensory 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/gittensory-commands

_{🟩 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