feat(github)!: rename the @gittensory bot mention command to @loopover

[JSONbored]

Summary

Phase 2 of #5705 (the gittensory -> loopover rebrand epic). Full cutover, no dual-recognition per explicit maintainer decision -- the @gittensory mention trigger, help text, and every generated PR-comment/API string mentioning "Gittensory" by name across the dispatch stack now say @loopover/"LoopOver".

• src/github/commands.ts's dispatch regex + entire command catalog, src/queue/processors.ts, src/api/routes.ts, and 20 other src/ files with live dispatch logic or generated public-facing text.
• A real duplicate implementation found mid-sweep: sanitizePublicComment() has an independent copy in packages/gittensory-engine/src/github/sanitize-public-comment.ts with its own "@gittensory "-prefix safelist check -- fixed in place. The two implementations should eventually be consolidated (follow-up, not done here -- flagging rather than scope-creeping this PR).
• scripts/gen-command-reference.mjs and scripts/check-docs-drift.mjs had their own hardcoded "@gittensory <id>" templates; regenerated apps/gittensory-ui/src/lib/command-reference.ts accordingly.
• 17 apps/gittensory-ui doc/site pages with their own @gittensory command examples (needed fixing for command-syntax accuracy -- distinct from general product-name prose across the UI, which is a much larger, separate surface deferred to a later phase).
• .loopover.yml.example + config/examples/*.yml comments, and renamed 6 config-example files whose names still said "gittensory" (config/examples/{gittensory.full,gittensory.minimal,global.gittensory,repo-override.gittensory,shared.gittensory}.yml, root .gittensory.minimal.yml) plus every file referencing them by name.

Regression caught and fixed mid-sweep: a blind rename in test/unit/queue-5.test.ts and src/github/app.ts had accidentally renamed references to the deliberately-preserved legacy check-run names ("Gittensory Gate" / "Gittensory Orb Review Agent", src/review/check-names.ts's GITTENSORY_LEGACY_* constants) into a nonsense "LoopOver Gate" string that collided with the real current check-run name and broke the upgrade-migration superseder logic. Reverted those specific legacy-detection references back to their correct historical values -- check-names.ts itself and its own dedicated test (test/unit/check-names.test.ts) were never touched.

Explicitly NOT in scope here (tracked separately in #5705): the MCP server's own "gittensory"-branded identity + 96 tool names (Phase 4), directory names (Phase 5), internal code identifiers like parseGittensoryMentionCommand (Phase 6), and general bare-prose "Gittensory" mentions scattered across ~40 additional src/ files that don't affect the mention command itself (found during this sweep, genuinely out of scope for this PR -- will need its own phase; #5705 will be updated to reflect the larger-than-originally-scoped surface).

Breaking change

The bot no longer recognizes @gittensory as a command trigger anywhere -- only @loopover works. Any saved PR-comment template, bookmark, or muscle-memory referencing @gittensory <command> must be updated to @loopover <command>.

Test plan

• npx tsc --noEmit --incremental false clean
• npm run docs:drift-check clean
• npm run command-reference regenerated + verified
• npm run test:coverage (unsharded, post-rebase): 832/832 test files, 16179/16179 tests pass, exit 0
• Specifically verified the legacy check-run superseder logic still works correctly (test/unit/check-names.test.ts, test/unit/queue-5.test.ts's gate-override-live-head regression) after reverting the accidental legacy-name rename

Refs #5705

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	8687062	Commit Preview URL Branch Preview URL	Jul 14 2026, 07:16 AM

[codecov]

❌ 7 Tests Failed:

Tests completed	Failed	Passed	Skipped
16178	7	16171	12

View the full list of 7 ❄️ flaky test(s)

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > actually narrows the PRs-tracked count to a selected $repo, and 'All' still includes every repo

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.0709s run time

AssertionError: expected '0' to be '3' // Object.is equality

Expected: "3"
Received: "0"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:478:22

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > adds local, webhook-observed issue-activity stat panels alongside the review_targets PR panels (#3716, switched off the GitHub API 2026-07)

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.019s run time

AssertionError: expected 'SELECT count(*) AS opened FROM issues…' to contain '(${repo:sqlstring} = \'$__all\' OR re…'

Expected: "(${repo:sqlstring} = '$__all' OR repo = ${repo:sqlstring})"
Received: "SELECT count(*) AS opened FROM issues WHERE (${repo:sqlstring} = '__ALL__' OR repo = ${repo:sqlstring}) AND unixepoch(created_at) >= ${__from:date:seconds} AND unixepoch(created_at) < ${__to:date:seconds}"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:343:33

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > drops a bot-authored release PR from the tracked-PR count and table (#4685-follow-up)

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.0389s run time

AssertionError: expected '0' to be '2' // Object.is equality

Expected: "2"
Received: "0"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:546:26

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > filters the pull request table to the selected time window

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.022s run time

AssertionError: expected '' to contain 'owner/repo|2|new|commented|comment|ne…'

- Expected
+ Received

- owner/repo|2|new|commented|comment|new row|2026-06-29T21:00:00Z

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:446:18

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > issue-activity panels count real rows correctly by state and window

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.0345s run time

AssertionError: expected '0' to be '2' // Object.is equality

Expected: "2"
Received: "0"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:416:20

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > scopes every review_targets panel query to the selected repo with Grafana SQL-string escaping

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.0053s run time

AssertionError: expected 'SELECT count(*) AS prs FROM review_ta…' to contain '(${repo:sqlstring} = \'$__all\' OR re…'

Expected: "(${repo:sqlstring} = '$__all' OR repo = ${repo:sqlstring})"
Received: "SELECT count(*) AS prs FROM review_targets WHERE (submitter NOT LIKE '%[bot]%' OR submitter IS NULL) AND (${repo:sqlstring} = '__ALL__' OR repo = ${repo:sqlstring}) AND unixepoch(updated_at) >= ${__from:date:seconds} AND unixepoch(updated_at) < ${__to:date:seconds}"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:384:32

test/unit/selfhost-grafana-dashboard.test.ts > maintainer Reviews & PRs Grafana dashboard > scopes the issue-activity panels to the selected $repo, same as the PR panels

Flake rate in main: 100.00% (Passed 0 times, Failed 4 times)

Stack Traces | 0.00671s run time

AssertionError: expected 'SELECT count(*) AS opened FROM issues…' to contain '(${repo:sqlstring} = \'$__all\' OR re…'

Expected: "(${repo:sqlstring} = '$__all' OR repo = ${repo:sqlstring})"
Received: "SELECT count(*) AS opened FROM issues WHERE (${repo:sqlstring} = '__ALL__' OR repo = ${repo:sqlstring}) AND unixepoch(created_at) >= ${__from:date:seconds} AND unixepoch(created_at) < ${__to:date:seconds}"

 ❯ test/unit/selfhost-grafana-dashboard.test.ts:361:44

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.