docs(miner): distinguish hosted vs stdio find_opportunities tool names

[JSONbored]

Summary

• cross-repo-discovery-phase1.md and an opportunity-ranker.ts comment described the hosted and stdio MCP surfaces as sharing one gittensory_-prefixed tool name. PR refactor(mcp): retire the loopover_/gittensory_ legacy tool-name aliases #5648 (part of the LoopOver rebrand epic Retire every deprecation shim #4777) renamed the stdio CLI's tool to loopover_find_opportunities; only the hosted server kept the gittensory_ prefix.
• Updates both references to name the correct tool per surface. Prose/comment only — no behavior change, no tests to update.

Test plan

• npm run test:ci — full local gate, clean (0 failures)

[superagent-security]

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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	3d94e41	Commit Preview URL Branch Preview URL	Jul 14 2026, 12:22 AM

[loopover-orb]

Warning

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

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-14 02:17:23 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
Pure documentation/comment update that corrects a stale claim (that hosted and stdio MCP tools share one `gittensory_`-prefixed name) to reflect the actual post-#5648 naming split: hosted keeps `gittensory_find_opportunities`, stdio uses `loopover_find_opportunities`. Changes are confined to a comment block in opportunity-ranker.ts and prose/table entries in cross-repo-discovery-phase1.md, with no code or behavior touched, so there's nothing to break. The opportunity-ranker.ts change flagged as having zero test-path evidence is expected since only a comment was edited, not the exported logic.

Nits — 3 non-blocking

• The doc still cites issue feat(mcp-cli): add gittensory_find_opportunities to the packages/gittensory-mcp stdio surface #2309 as 'Stdio `loopover_find_opportunities`' without a pointer to refactor(mcp): retire the loopover_/gittensory_ legacy tool-name aliases #5648 in that specific table row (only the prose sentence above links it), so a reader skimming just the table won't see the rename context.
• Consider adding a one-line note near the feat(mcp-cli): add gittensory_find_opportunities to the packages/gittensory-mcp stdio surface #2309 table row (cross-repo-discovery-phase1.md) linking to refactor(mcp): retire the loopover_/gittensory_ legacy tool-name aliases #5648 for consistency with the prose sentence above it.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

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: 45 registered-repo PR(s), 37 merged, 330 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 45 PR(s), 330 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	⚠️ ℹ️ None detected	risk: low · value: none — No structural-improvement signals were detected for this PR.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 45 PR(s), 330 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.
• 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