chore: fix gittensory -> loopover rename residue in docs

[JSONbored]

Closes #6074. Small, mechanical, prose-only.

Summary

• README.md:3 read "Formerly LoopOver." — self-referential nonsense; now correctly credits the actual former name, Gittensory.
• config/examples/README.md referred to the manifest starter as gittensory.yml and named gittensory in a fleet-notes list, inconsistent with the SAME file's own line 17 ("The canonical manifest filename is .loopover.yml").
• config/examples/TEMPLATES.md had a ### \JSONbored/gittensory` (dogfooding)section heading and a"Same split as `gittensory`"reference — both should sayloopover/JSONbored/loopover, matching every other template reference in the same file (.loopover.yml, loopover.minimal.yml, loopover-config/`, etc.).

Deliberately NOT touched

• The docs badge domain (gittensory.aethereal.dev) — per prior rename-status context, the website/cloud-presentation layer is a distinct, intentionally-hardcoded surface from the engine rename; I don't have confirmation this domain itself was renamed (vs. the GitHub repo/npm packages/directory paths, which were), so changing it risked breaking a real working link rather than fixing residue. Flagging rather than guessing.
• The legacy comment renderer's <!-- gittensory-pr-panel:v1 --> HTML marker — this is load-bearing for the comment-upsert match logic (markerAliases()), so a straight rename risks orphaning in-flight PR comments; it needs an additive alias, not a rename, and is better handled alongside whatever comes out of investigate: is the legacy comment renderer still needed anywhere? #6073 (the legacy-renderer-retirement investigation) rather than as an isolated prose fix.

Test plan

• npm run docs:drift-check — pass
• git diff --check clean
• Grepped every root doc (SUPPORT.md, CODE_OF_CONDUCT.md, SECURITY.md, CONTRIBUTING.md, AGENTS.md) for the same self-referential rename bug — none found

[superagent-security]

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

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-15 09:01:55 UTC}

3 files · 1 AI reviewer · no blockers · readiness 80/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a pure prose/documentation fix that corrects leftover 'gittensory' naming residue in three files, replacing it with the correct 'loopover' name and fixing a self-referential README line that previously read 'Formerly LoopOver' to correctly say 'Formerly Gittensory.' The changes are consistent with the stated intent, each replacement matches surrounding context (e.g. config/examples/README.md now aligns with its own line 17 canonical filename claim), and the diff closes issue #6074 as described. No code, schema, or logic is touched, so there is no functional risk.

Nits — 3 non-blocking

• The PR description mentions deliberately not touching the gittensory.aethereal.dev badge domain and the legacy `<!-- gittensory-pr-panel:v1 -->` marker — worth double-checking no other doc references the same domain/marker inconsistently, though this is out of scope for this PR.
• Consider a repo-wide grep for 'gittensory' as a follow-up to catch any remaining residue outside the root docs already checked (e.g. inline code comments or CI config), separate from this PR's scope.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#6074
Related work	⚠️ 2 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 43 registered-repo PR(s), 35 merged, 360 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 43 PR(s), 360 issue(s).
Gate result	✅ Passing	No configured blocker found.
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal · LLM: minor

Linked issue satisfaction

Partially addressed
The PR fixes the README self-reference and both config/examples doc filename references as requested, but explicitly leaves the docs badge domain and the HTML marker rename untouched, and the marker item wasn't even converted into the requested alias investigation/fix.

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: not available
• Official Gittensor activity: 43 PR(s), 360 issue(s).
• Related work: Items reference the same linked issue chore: fix gittensory -> loopover rename residue #6074. (issue #6074)
• Related work: Open PR work references issue chore: fix gittensory -> loopover rename residue #6074. (issue #6074)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 3 steps in the Signals table above.

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.

🧪 Chat with LoopOver

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

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

🧪 Experimental — new and may change.

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

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