docs: rename gittensory prose to loopover in README and config example

[JSONbored]

Summary

• Part of the gittensory→loopover rebrand (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705), phase 8b: rename brand-name prose in README.md (badge/link URLs now point at the renamed JSONbored/loopover repo) and config/examples/loopover.full.yml (comments only, no schema/example-value change).

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves — N/A, maintainer-authored rebrand-epic cleanup (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705), no linked-issue gate applies to owner PRs.

Validation

• git diff --check
• Docs-only diff (README.md, one YAML comment file), no code/schema affected

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — N/A, no such changes.
• API/OpenAPI/MCP behavior is updated and tested where needed. — N/A, docs only.
• UI changes use live API data or real empty/error/loading states. — N/A, no UI changes.
• Visible UI changes include a UI Evidence section. — N/A, no UI changes.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs (none touched here).

Notes

• One of several batched PRs covering the bulk-prose portion of rebrand epic Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705.

[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-14 22:01:10 UTC}

2 files · 1 AI reviewer · 1 blocker · readiness 77/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
Mechanical phase-8b rename of remaining 'gittensory' prose to 'loopover' in README.md badge/link URLs and comment-only prose in config/examples/loopover.full.yml. The diff carefully distinguishes the product brand (gittensory→loopover) from the separate 'gittensor' subnet/network name, which is correctly left untouched throughout (e.g. 'experimental: gittensor: true', 'Gittensor Contributor Impact' heading). It leaves the docs domain badge (gittensory.aethereal.dev) unrenamed, consistent with the PR's stated scope of only badge/link URLs pointing at the GitHub repo itself.

Nits — 5 non-blocking

• README.md still references 'https:​//gittensory.aethereal.dev/docs' for the Docs badge and text — worth confirming that domain rename is tracked in a later phase of Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705 rather than being missed.
• config/examples/loopover.full.yml:1170-1180 renames 'gittensory' to 'loopover' in prose but leaves 'gittensor' (subnet) references as-is — correct per the brand/network distinction, but worth a one-line note in the PR description clarifying this distinction was intentional so future rebrand-phase reviewers don't flag it as inconsistent.
• Consider a follow-up grep across the repo for residual 'gittensory' occurrences outside README.md/config/examples to confirm phase 8b fully closes out the prose-rename sweep for these two files.
• If the docs domain (gittensory.aethereal.dev) is slated for rename too, link that as an explicit upcoming phase in the Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705 tracking issue so it isn't dropped.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

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.

📋 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.

Signal	Result	Evidence
Code review	❌ 1 blocker	1 reviewer
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High 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, 385 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 43 PR(s), 385 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	⚠️ ℹ️ Insufficient signal	risk: low · 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, purely mechanical prose/URL rename batch that incrementally advances the larger rebrand epic without touching code, schema, or behavior.

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: not available
• Official Gittensor activity: 43 PR(s), 385 issue(s).
• Related work: Titles/paths share 5 meaningful terms. (PR #5897)
• Related work: Titles/paths share 5 meaningful terms. (PR #5895)
• Related work: Titles/paths share 5 meaningful terms. (PR #5896)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Review top overlaps.
• Add a concise scope and risk note.
• Triage stale or unlinked PRs.
• No action.
• Check active issues and PRs before submitting.

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