diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8243a9fa49..e874a551b7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -282,7 +282,7 @@ Public GitHub surfaces:
app/infra state) resolves to a neutral, non-blocking gate. Adding a blocker must keep it
confirmed-contributor-gated through `evaluateGateCheck`.
-Config as code (`.gittensory.yml`) — every repository setting is controllable from the config file:
+Config as code (`.loopover.yml`; the legacy `.gittensory.yml` filename is dual-read indefinitely, #4773) — every repository setting is controllable from the config file:
- **`settings:`** is a partial of the repository settings: any behaviour a maintainer can toggle in the
dashboard can be set here as code — `commentMode`, `publicAudienceMode`, `publicSurface`, `checkRunMode`,
@@ -296,14 +296,15 @@ Config as code (`.gittensory.yml`) — every repository setting is controllable
`validationEvidence`, `openPrQueue`, `contributorContext`, `gateResult`). Maintainer text that fails the
public-safe filter (reward/score/wallet/hotkey/etc.) is dropped, never published.
- **`repoDocGeneration:`** opts a repo into the AGENTS.md/CLAUDE.md generation roadmap (#2993) — a
- `.gittensory.yml`-only surface with no dashboard/DB counterpart. `enabled` (default `false`) turns it on;
+ `.loopover.yml`-only surface with no dashboard/DB counterpart. `enabled` (default `false`) turns it on;
`scope` (default `["agents"]`) picks which generated file types are in play (`"agents"` for
AGENTS.md/CLAUDE.md, plus `"skills"` once skill-file generation lands); `allowOverwriteExisting` (default
`false`) is a separate opt-in required before the engine proposes an overwrite for a repo that already has
a hand-maintained AGENTS.md/CLAUDE.md — absent it, an existing hand-written file is left alone and
generation is skipped.
-- Precedence: `.gittensory.yml` `gate:` > `.gittensory.yml` `settings:` > dashboard repository settings >
- safe defaults; unset fields fall back to the next layer. The committed root `.gittensory.yml` is the
+- Precedence: `.loopover.yml` `gate:` > `.loopover.yml` `settings:` > dashboard repository settings >
+ safe defaults; unset fields fall back to the next layer (the legacy `.gittensory.yml` filename works
+ identically wherever `.loopover.yml` does, #4773). The committed root `.gittensory.yml` is the
worked example. Resolved once in `resolveRepositorySettings`, so the whole app honours the file.
- The config chooses **what** LoopOver does (gate on/off, blockers, comments, labels, surface, panel
content); it never changes **who** can be blocked — only confirmed Gittensor contributors are ever
diff --git a/README.md b/README.md
index 780cffe324..f4a7d607c5 100644
--- a/README.md
+++ b/README.md
@@ -37,16 +37,16 @@ LoopOver CI and LoopOver review score, gate, and comment on pull requests. The r
- **CI + full-file grounding** — grounds the AI reviewer with the PR's finished CI status and the full post-change content of the changed files, so claims are verified against reality instead of predicted.
- **Codebase RAG** — retrieval-augmented context that queries the codebase vector index for related callers, modules, and conventions and appends them to the reviewer prompt (additive only; inert until an index exists).
- **Submitter-reputation gating** — an internal-only spend control that downgrades new / burst / low-reputation submitters to a deterministic-only review, never surfaced on any public comment, label, or check.
-- **Unified review comment** — renders the public PR feedback as one in-place comment instead of multiple panels. With `.gittensory.yml`'s `review.changed_files_summary` also on (off by default), it gains a deterministic, no-AI "Changed files" collapsible: one row per file category (source/test/docs/config/generated), with file counts and +/- totals.
+- **Unified review comment** — renders the public PR feedback as one in-place comment instead of multiple panels. With `.loopover.yml`'s `review.changed_files_summary` also on (off by default; legacy `.gittensory.yml` name also still works, indefinitely), it gains a deterministic, no-AI "Changed files" collapsible: one row per file category (source/test/docs/config/generated), with file counts and +/- totals.
- **Per-repo activation** — capabilities roll forward (and back) one flag and one repo at a time via the `GITTENSORY_REVIEW_REPOS` allowlist.
**Check-run and comment surfaces, disambiguated** (a common point of confusion — these are three independent, separately-configured things, not layers of the same feature):
- **`LoopOver Orb Review Agent`** (`gate.*` / `settings.reviewCheckMode`, off by default) — the authoritative GitHub Check Run carrying the gate's pass/fail verdict. This is the one worth making a required status check.
- **`LoopOver Context`** (`settings.checkRunMode` / `settings.checkRunDetailLevel`, off by default) — a separate, purely advisory Check Run. At its default `checkRunDetailLevel: minimal` it publishes no findings at all; even at `standard`/`deep` it only re-renders content already shown elsewhere. Never make this one required.
-- **Inline review comments** (`GITTENSORY_REVIEW_INLINE_COMMENTS` + `.gittensory.yml`'s `review.inline_comments`, off by both by default) — real, reply-able line-anchored PR review comment threads (CodeRabbit-style). This is the ONLY one of the three that posts an interactive per-line thread; the two check runs above never do. With `.gittensory.yml`'s `review.suggestions` also on, a precise line-anchored fix is additionally rendered as a one-click, committable GitHub suggested-change block. With `review.finding_categories` also on (off by default), each finding is additionally tagged with a category — security/correctness/performance/maintainability/tests/style — in both the inline comment label and the unified comment's "Finding categories" collapsible; a deterministic path/keyword fallback covers whatever the model omits.
+- **Inline review comments** (`GITTENSORY_REVIEW_INLINE_COMMENTS` + `.loopover.yml`'s `review.inline_comments`, off by both by default) — real, reply-able line-anchored PR review comment threads (CodeRabbit-style). This is the ONLY one of the three that posts an interactive per-line thread; the two check runs above never do. With `.loopover.yml`'s `review.suggestions` also on, a precise line-anchored fix is additionally rendered as a one-click, committable GitHub suggested-change block. With `review.finding_categories` also on (off by default), each finding is additionally tagged with a category — security/correctness/performance/maintainability/tests/style — in both the inline comment label and the unified comment's "Finding categories" collapsible; a deterministic path/keyword fallback covers whatever the model omits.
-See [Tuning your reviews](https://gittensory.aethereal.dev/docs/tuning) for the full flag, setting, and `.gittensory.yml` reference.
+See [Tuning your reviews](https://gittensory.aethereal.dev/docs/tuning) for the full flag, setting, and `.loopover.yml` reference (the legacy `.gittensory.yml` filename is dual-read indefinitely — #4773 — so an existing repo's committed file keeps working unchanged).
## Start Here
diff --git a/apps/gittensory-ui/src/components/site/app-panels/ai-provider-mode-field-group.tsx b/apps/gittensory-ui/src/components/site/app-panels/ai-provider-mode-field-group.tsx
index 1a9dea2e1d..290533d480 100644
--- a/apps/gittensory-ui/src/components/site/app-panels/ai-provider-mode-field-group.tsx
+++ b/apps/gittensory-ui/src/components/site/app-panels/ai-provider-mode-field-group.tsx
@@ -66,8 +66,8 @@ export function AiProviderModeFieldGroup({
- The exact .gittensory.yml files. This field group only records
- mode and model names.
+ .loopover.yml files. This field group only records mode
+ and model names.
Preview
.gittensory.yml this configuration would
- produce. Nothing is saved until you copy it into your repo.
+ The exact .loopover.yml this configuration would produce
+ (the legacy .gittensory.yml name also still works).
+ Nothing is saved until you copy it into your repo.
The repo's maintainer focus policy as JSON — wanted paths, linked-issue policy, test
- expectations, and gate overrides. Mirrors .gittensory.yml
- .
+ expectations, and gate overrides. Mirrors .loopover.yml.