From 66675da610dc3356cee4dfff32a4644751298cde Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Sun, 26 Jul 2026 23:25:27 -0700
Subject: [PATCH] fix(review): correct a stray gittensory reference to loopover
 in a doc comment

Trips the branding-drift check, which was already red on main independent
of any other change -- a one-word rename leftover in a comment.
---
 src/review/predicted-gate-agreement.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/review/predicted-gate-agreement.ts b/src/review/predicted-gate-agreement.ts
index 4214e49373..726ef4dfc6 100644
--- a/src/review/predicted-gate-agreement.ts
+++ b/src/review/predicted-gate-agreement.ts
@@ -1,6 +1,6 @@
 // Predicted-vs-live gate agreement (#predicted-live-gate-agreement, maintainer review-stack x AMS integration
 // audit 2026-07-09) -- a SIBLING to computeGateEval/computeGateParity (src/review/parity.ts), answering a
-// DIFFERENT question than either: not "does gittensory match reviewbot" (computeGateParity) and not "does one
+// DIFFERENT question than either: not "does loopover match reviewbot" (computeGateParity) and not "does one
 // system's prediction match the human's realized merge/close" (computeGateEval), but "does the MCP predict_gate
 // tool's pre-submission verdict for a contributor match the REAL gate decision their eventual PR receives."
 //