fix(review): restore engine-parity after gittensory rename drift

packages/loopover-engine/src/review/guardrail-config.ts

@@ -32,7 +32,7 @@ export const ENGINE_DECISION_GUARDRAIL_GLOBS = [
   "src/github/pr-actions.ts",
   "src/github/app.ts",
   "src/github/backfill.ts",
-  // #4197: writes a real commit onto a CONTRIBUTOR's own PR branch (not a branch gittensory owns) — the same
+  // #4197: writes a real commit onto a CONTRIBUTOR's own PR branch (not a branch loopover owns) — the same
   // guardrail tier as pr-actions.ts/app.ts for the same reason, a new GitHub-write surface.
   "src/github/e2e-test-commit.ts",
   "src/scoring/**",

packages/loopover-engine/src/review/linked-issue-label-propagation.ts

@@ -10,7 +10,7 @@ export type { LinkedIssueLabelPropagationConfig, LinkedIssueLabelPropagationMapp
 // (replaces the normal bug/feature type label, like priority does) or additive (applied alongside it).
 //
 // PURE config types + normalizer only — no GitHub/fetch/Env-dependent imports. `focus-manifest.ts`'s YAML
-// parser imports this module directly, and `focus-manifest.ts` is itself pulled into the gittensory-ui
+// parser imports this module directly, and `focus-manifest.ts` is itself pulled into the loopover-ui
 // workspace's isolated typecheck (via `apps/loopover-ui/src/lib/registration-workspace.ts`), which has no
 // visibility into the Worker's ambient `Env` type. The actual GitHub fetch orchestrator
 // (`fetchLinkedIssueLabelsForPropagation`) lives in `linked-issue-label-propagation-fetch.ts` instead, kept

test/unit/finding-taxonomy.test.ts

@@ -23,6 +23,6 @@ describe("finding taxonomy document", () => {
   });
 
   it("uses the stable MCP resource URI", () => {
-    expect(FINDING_TAXONOMY_URI).toBe("gittensory://finding-taxonomy");
+    expect(FINDING_TAXONOMY_URI).toBe("loopover://finding-taxonomy");
   });
 });