docs: fix post-rebrand dead gittensory-* references in contributor docs

[lourincedaging0-commits]

Summary

The gittensory → loopover rebrand (#5705) renamed the CLI binaries, package directories, and Cloudflare Worker names, but four contributor-facing doc files still cited the pre-rename names. This fixes them against the live source-of-truth:

• CONTRIBUTING.md — Worker names → loopover-ui / loopover-api (per apps/loopover-ui/wrangler.jsonc and root wrangler.jsonc); MCP bin → loopover-mcp init-client --print (per packages/loopover-mcp/package.json).
• packages/loopover-miner/README.md — two broken relative links pointing at the renamed packages/gittensory-engine / packages/gittensory-mcp directories → packages/loopover-engine / packages/loopover-mcp.
• .claude/skills/contributing-to-loopover/SKILL.md & reference.md — copy-pasteable gittensory-mcp commands (dead bin) → loopover-mcp; the gittensory-ui visual-review mention → loopover-ui; the dead @jsonbored/gittensory-{engine,miner} package names → @loopover/{engine,miner}.

Deliberately left unchanged (verified)

• gittensory.aethereal.dev / gittensory-api.aethereal.dev hostnames — apps/loopover-ui/wrangler.jsonc still routes gittensory.aethereal.dev and the root config documents the old domain as intentionally still-live post-rebrand (Decide & schedule the domain sunset window #4765). The fix here is the Worker name a contributor looks up in the Cloudflare dashboard, not the live route.
• JSONbored/gittensory repo URLs and the screenshots worktree/branch derived from the repo name — the repo redirect is live and the issue itself keeps these.
• [mcp_servers.gittensory] config key — the MCP server identifier was not renamed, only its binary.

Notes

Docs-only (*.md) change — outside codecov.yml's coverage.include, so the patch/project gates don't fire (expected). Every renamed target already exists on main; only the doc text lagged.

Closes #5809

[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:12:50 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This is a straightforward docs-only fix that replaces stale `gittensory-*` binary/package/worker references with their live post-rebrand `loopover-*` equivalents across CONTRIBUTING.md, two `.claude/skills` files, and the miner README, while deliberately preserving the still-live `gittensory.aethereal.dev` hostnames and the unrenamed `[mcp_servers.gittensory]` config key. The two relative-link fixes in `packages/loopover-miner/README.md` (pointing at `../loopover-engine/...` and `../loopover-mcp/README.md`) correctly resolve given the file's location under `packages/loopover-miner/`, matching the described renamed directories. The diff is narrow, internally consistent, and matches its stated intent with no code paths touched.

Nits — 3 non-blocking

• CONTRIBUTING.md:250-251 still documents the live `gittensory.aethereal.dev` / `gittensory-api.aethereal.dev` hostnames right next to the renamed Worker names — consider a one-line note there (as the PR description already does) so a reader isn't confused why the name changed but the URL didn't.
• reference.md and SKILL.md both retain the literal string `[mcp_servers.gittensory]` in the printed CLI comment — worth double-checking this still matches the actual TOML key `loopover-mcp init-client --print codex` emits today, since it's the one identifier in these files not touched by the rename.
• None beyond the nits above — the change is well-scoped and doesn't need further edits.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#5809
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	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 61 registered-repo PR(s), 24 merged, 4 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	lourincedaging0-commits; Gittensor profile; 61 PR(s), 4 issue(s).
Gate result	✅ Passing	No configured 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 — The change corrects dead/stale binary and path references left over from a prior rebrand in contributor-facing docs, which is a small but real correctness improvement with no functional code impact.

Linked issue satisfaction

Addressed
The diff updates all four required files exactly as specified: CONTRIBUTING.md's Worker names and MCP command, both broken relative links in loopover-miner/README.md, and the gittensory-mcp/gittensory-ui references in SKILL.md and reference.md.

Review context

• Author: lourincedaging0-commits
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 61 PR(s), 4 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Await review-lane availability.
• Refresh registry data or choose a registered active repo.

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

[loopover-orb]

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