docs(core): rename gittensory prose to loopover in signals/selfhost/services

[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 comments across src/signals/**, src/selfhost/**, and src/services/** (31 files). Comment-only, plus one tmpdir-prefix rename in src/selfhost/ai.ts (gittensory-ai- → loopover-ai-) with its matching test/unit/selfhost-ai.test.ts assertion updated in the same commit.
• Includes the matching packages/loopover-engine/src/signals/change-guardrail.ts twin fix so scripts/check-engine-parity.ts stays passing.
• Deliberately left untouched: src/services/notify-pagerduty.ts's deliberate backward-compat dual actor-check (queries both "loopover" and legacy "gittensory" audit-actor values across the rebrand cutover boundary — real, intentional, not a gap), the 'gittensory-native' review_audit.source discriminator, and GITTENSORY-[A-Z0-9]+ Sentry issue slug references.

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
• npx tsx scripts/check-engine-parity.ts — ok
• npm run typecheck — clean
• npm run test:coverage — full unsharded run, 100% green (verified locally before this rebase)

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, comment-only, no behavior change.
• 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]

Caution

🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-14 23:30:52 UTC}

35 files · 1 AI reviewer · 1 blocker · readiness 77/100 · CI failing · blocked

🛑 Suggested Action - Manual Review

Review summary
This is a mechanical comment/prose rename from gittensory to loopover across signals/selfhost/services, plus the tmpdir prefix rename in src/selfhost/ai.ts (gittensory-ai- → loopover-ai-) with matching test assertions updated, and the WEBHOOK_SECRET_BY_REPO key rename in notify-discord.ts. The change is comment-only except for the tmpdir prefix and the Discord webhook repo-key string, both of which have corresponding logic/test updates in the same diff, so runtime behavior is preserved. The change-guardrail.ts twin edit in packages/loopover-engine keeps check-engine-parity passing as claimed.

Nits — 4 non-blocking

• src/services/notify-discord.ts:27 — confirm no external system or config still sends webhooks keyed by the literal string "jsonbored/gittensory" (case-sensitive map lookup), since this rename is a silent behavior change if the repo full name source ever still resolves to the old slug.
• test/unit/selfhost-ai.test.ts:1418 — the substring assertion `toContain("loopover-ai-")` is fine but relies on the tmpdir prefix staying exactly in sync with ai.ts:523; low risk given both changed in the same commit.
• Double check any deployment/ops scripts or .env examples outside this diff that might reference `jsonbored/gittensory` as a Discord webhook routing key, since PR scope excludes non-src files.
• Pull request duplicates other open work — Check for an existing pull request or issue covering this change and coordinate or consolidate before continuing.

Why this is blocked

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

CI checks failing

• validate
• validate-tests (2)

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, 373 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 43 PR(s), 373 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	✅ Minor	risk: low · value: minor — Code changes are accompanied by test evidence.

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), 373 issue(s).
• Related work: Titles/paths share 9 meaningful terms. (PR #5897)
• Related work: Titles/paths share 10 meaningful terms. (PR #5895)
• Related work: Titles/paths share 9 meaningful terms. (PR #5897, PR #5895)

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