docs(engine): rename gittensory prose to loopover in packages/loopover-engine (batch A)

[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 19 packages/loopover-engine/src/**/*.ts files (advisory, duplicate detection, focus-manifest, index, issue-rag-query, local-scorer, miner-prediction-metrics, the miner subsystem, prompt-packet, and review content-lane/guardrail modules), plus src/rules/advisory.ts. Comment-only, except:
  • local-scorer.ts's activeModel: "gittensory-deterministic" value — an internal, non-persisted string with no external consumer besides its own test, updated in the same commit.
  • src/rules/advisory.ts and packages/loopover-engine/src/advisory/gate-advisory.ts share a deliberately-divergent gate-decision marker pair (GATE_DECISION_TWIN_PAIR in scripts/check-engine-parity.ts) that must change together in one PR — both renamed here.
• Two files in this batch (review/guardrail-config.ts, review/linked-issue-label-propagation.ts) are byte-identical twins of already-renamed host files (src/review/**); this batch picks up main's already-correct state for them via rebase, so scripts/check-engine-parity.ts stays green.

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 (verified with a real base-ref, matching CI)
• npm run typecheck — clean

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-15 00:02:01 UTC}

20 files · 1 AI reviewer · 1 blocker · readiness 95/100 · CI failing · blocked

🛑 Suggested Action - Manual Review

Review summary
Comment-only rebrand rename of gittensory→loopover prose across 19 files in packages/loopover-engine, plus one internal test-only string constant (`activeModel`) updated consistently in both source and its test. The change is mechanical, low-risk, and self-contained; no behavioral or API surface changes are introduced, and the string-literal update is correctly paired with its corresponding test assertion update.

Nits — 3 non-blocking

• local-scorer.ts:59 the `activeModel` string change is a value, not prose — worth flagging explicitly in the PR description as intentional (which it already is) so future rebrand batches don't assume this file is comment-only by pattern-matching the title.
• Given this is a maintainer-authored, mechanical, no-linked-issue cleanup PR per the epic (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705), consider batching more files per PR if `check-engine-parity.ts` and typecheck stay green, to reduce total PR count for this rebrand.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

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 (6)

Signal	Result	Evidence
Code review	❌ 1 blocker	1 reviewer
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
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: 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	⚠️ ℹ️ None detected	risk: low · value: none — No structural-improvement signals were detected for this PR.

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).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Triage stale or unlinked PRs.
• No action.

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