refactor(mcp): retire the loopover_/gittensory_ legacy tool-name aliases

[JSONbored]

Issue #4775 renamed the local stdio MCP CLI's 37 tools from
gittensory_-prefixed to loopover_-prefixed names, keeping the old
names registered as deprecated aliases (registerToolWithLegacyAlias)
during a transition window. Remove that mechanism: each tool now
registers once, under its canonical loopover_ name only.

Deletes legacyAliasName() and ALL_STDIO_TOOL_DESCRIPTORS (the
37-primary + 37-alias merged descriptor list), collapsing
stdioToolDescription() and the tools CLI subcommand back to the
original 37-entry STDIO_TOOL_DESCRIPTORS.

Deliberately unchanged: AGENT_PROFILES.recommendedTools/recommendedPrompts
still reference several gittensory_-prefixed names. Most of those
belong to the separate, never-renamed remote/hosted MCP server
(src/mcp/server.ts), not these local CLI tools. A handful do collide
with locally-renamed tools (gittensory_agent_plan_next_work and 7
others) -- left exactly as-is pending a maintainer call on whether
those specific references were meant to track the local rename,
since test/unit/mcp-cli-basics.test.ts pins this exact spelling today.

Part of #4777

[superagent-security]

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

[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.03%. Comparing base (941c300) to head (92ddd5a).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5648   +/-   ##
=======================================
  Coverage   95.03%   95.03%           
=======================================
  Files         577      577           
  Lines       45920    45920           
  Branches    14695    14695           
=======================================
  Hits        43640    43640           
  Misses       1528     1528           
  Partials      752      752           

Flag	Coverage Δ
shard-1	43.91% <ø> (ø)
shard-2	35.67% <ø> (ø)
shard-3	32.26% <ø> (+0.06%)	⬆️
shard-4	32.69% <ø> (+0.11%)	⬆️
shard-5	31.74% <ø> (-0.04%)	⬇️
shard-6	44.46% <ø> (ø)

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[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	92ddd5a	Commit Preview URL Branch Preview URL	Jul 13 2026, 07:51 PM

[loopover-orb]

Warning

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

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-13 19:54:13 UTC}

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

⏸️ Suggested Action - Manual Review

• AI review could not be completed: The dual-model AI review did not return a usable verdict for this change.

Review summary
This PR cleanly retires the loopover_/gittensory_ deprecated-alias mechanism from #4775: registerToolWithLegacyAlias is replaced with a plain registerStdioTool wrapper, ALL_STDIO_TOOL_DESCRIPTORS and legacyAliasName() are deleted, and stdioToolDescription()/toolsCommand() fall back to the original 37-entry STDIO_TOOL_DESCRIPTORS. The test suite is correctly updated to assert the new invariants (37 tools, zero gittensory_-prefixed aliases, retired names error rather than resolve), and docs/skill references to the now-dead aliases are stripped. The PR explicitly and honestly flags an unresolved edge case — several AGENT_PROFILES entries and docs still reference gittensory_-prefixed names that collide with locally-renamed tools (e.g. gittensory_agent_plan_next_work) — and defers that to a maintainer call rather than silently leaving stale references.

Nits — 6 non-blocking

• The PR's own description flags that AGENT_PROFILES.recommendedTools/recommendedPrompts still reference gittensory_-prefixed names that collide with 7 locally-retired tools (e.g. gittensory_agent_plan_next_work) — worth a maintainer decision before merge so agent profiles don't silently reference dead tool names.
• test/unit/mcp-tool-rename-aliases.test.ts's retired-alias test passes empty arguments ({}) for tools like gittensory_get_repo_context that require owner/repo — verify the isError:true assertion is actually due to 'unknown tool' rather than a schema-validation error that would pass even if the alias accidentally still resolved.
• registerStdioTool(name, config, handler) is now a pure pass-through to server.registerTool with no added behavior — consider whether keeping the wrapper (vs. calling server.registerTool directly at all 37 call sites) is worth the indirection now that there's no alias logic to share.
• Confirm with a maintainer whether the 7 colliding gittensory_-prefixed AGENT_PROFILES references (e.g. gittensory_agent_plan_next_work) should be renamed to loopover_ now, since test/unit/mcp-cli-basics.test.ts reportedly pins the old spelling.
• In mcp-tool-rename-aliases.test.ts, tighten the retired-alias assertions by checking the error message/content mentions 'Unknown tool' or similar, not just isError:true, to guard against a false pass from unrelated validation errors.
• AI review could not be completed — The gate is held for a human reviewer rather than passed automatically; it re-evaluates on the next update.

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: 44 registered-repo PR(s), 36 merged, 320 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 320 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	✅ Minor	risk: clean · value: minor — Code changes are accompanied by test evidence. LLM value judgment: moderate — This completes a previously-planned two-phase deprecation (#4775 introduce aliases, #4777 retire them), removing real dead code (legacyAliasName, ALL_STDIO_TOOL_DESCRIPTORS) and updating tests/docs in lockstep, though it stops short of resolving the residual AGENT_PROFILES naming collisions it surfaces.

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: 44 PR(s), 320 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