refactor(rebrand): update GitHub App slug to loopover-orb

[JSONbored]

Summary

• Closes GitHub App rename #4772. The GitHub App itself was renamed "Gittensory Orb" → "Loopover ORB" directly in GitHub settings (confirmed resulting slug: loopover-orb, via a live fetch to https://github.com/apps/loopover-orb) — an in-place rename, not a new App registration, so existing installations and webhook deliveries are unaffected (keyed by the App's immutable ID, not its slug).
• Also updated on GitHub's side as part of the same change:
  • Homepage URL → https://loopover.ai
  • A second OAuth callback URL added for https://api.loopover.ai/v1/orb/oauth/callback (the old gittensory-api.aethereal.dev one stays registered until the PUBLIC_API_ORIGIN flip lands separately)
  • Webhook URL → https://api.loopover.ai/v1/orb/webhook (safe immediately — that domain already routes to the same live Worker as the old one, from the earlier domain-wiring work)
• Code-side, the only real reference to the App's actual slug is PUBLIC_GITHUB_APP_SLUG in src/services/subnet-interface.ts — a hardcoded product-identity constant (not env-driven) used to build the install-URL descriptor served to the Bittensor subnet registry. Updated it + the two tests asserting its value.

What was deliberately NOT touched

• Every other mention of gittensory-orb/gittensory-orb[bot] across the test suite (self-authored-detection fixtures, webhook sender-login test data) belongs to a different, already-fully-deleted review App (its own GITHUB_APP_SLUG env var was removed from wrangler.jsonc back on 2026-07-12). Those are arbitrary, internally-consistent test strings unrelated to the Orb App's real identity, not production values.
• apps/gittensory-ui/src/routes/docs.self-hosting-release-checklist.tsx's gittensory-orb@0.1.0 Sentry-release-id mention is a historical record of an actual past release and is deliberately never edited, same as CHANGELOG.md.

Test plan

• Full local gate (npm run test:ci + npm audit --audit-level=moderate) green.
• Confirmed via a live fetch to https://github.com/apps/loopover-orb that the App rename produced exactly the expected slug before touching any code.

[superagent-security]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.01%. Comparing base (1021569) to head (38fdba4).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5612   +/-   ##
=======================================
  Coverage   95.01%   95.01%           
=======================================
  Files         574      574           
  Lines       45684    45684           
  Branches    14661    14661           
=======================================
  Hits        43405    43405           
  Misses       1528     1528           
  Partials      751      751           

Flag	Coverage Δ
shard-1	43.95% <100.00%> (-0.05%)	⬇️
shard-2	35.78% <100.00%> (+0.05%)	⬆️
shard-3	32.14% <100.00%> (-0.10%)	⬇️
shard-4	30.86% <100.00%> (-1.76%)	⬇️
shard-5	32.65% <100.00%> (+0.89%)	⬆️
shard-6	44.46% <100.00%> (+0.38%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/services/subnet-interface.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

Important

🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪

🔍 Gittensory is reviewing…

AI analysis is in progress. This comment will update when the review is complete.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing}

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-13 09:35:37 UTC}

3 files · 2 AI reviewers · no blockers · readiness 100/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review: This PR changes guardrail-protected path(s): src/services/subnet-interface.ts (matched src/services/**).

Review summary
Small, well-contained rename PR: updates the hardcoded PUBLIC_GITHUB_APP_SLUG constant from "gittensory-orb" to "loopover-orb" and the two tests that assert its value, matching the description that the GitHub App was renamed in-place on GitHub's side. The full file content confirms the constant is used consistently to build both the descriptor's slug and installUrl, so the change is internally coherent and both call sites (unit and integration tests) are updated together. This closes issue #4772 and is narrowly scoped, touching only the identity constant and its direct test assertions.

Nits — 7 non-blocking

• The PR description mentions webhook/OAuth callback URL changes made on GitHub's side, but nothing in the diff verifies these against any code-side config; if those URLs are ever hardcoded elsewhere in the codebase (not shown here), confirm they don't need updating too.
• Consider a follow-up issue/PR to track the deferred `PUBLIC_API_ORIGIN` flip and removal of the old OAuth callback URL, per the description.
• nit: `src/services/subnet-interface.ts:25` still tells maintainers to install the "Gittensory GitHub App" even though this PR says the public App was renamed to Loopover ORB, so either update that user-facing onboarding string or explain why the old product name is intentionally retained there.
• `src/services/subnet-interface.ts:25` could say `Maintainers: install the Loopover ORB GitHub App on a gittensor-registered repository.` to keep the descriptor’s onboarding copy aligned with the new slug.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	2 reviewers, synthesized
Linked issue	✅ Linked	#4772
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 347 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 347 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
Improvement	⚠️ ℹ️ None detected	risk: low · value: none — No structural-improvement signals were detected for this PR. LLM value judgment: minor — The diff is a narrowly-scoped, mechanical constant rename tied to an already-completed external GitHub App rename, correctly closing issue #4772 with consistent test updates.

Linked issue satisfaction

Partially addressed
The App rename itself and the code's one real slug reference (subnet-interface.ts plus its tests) are updated and match the acceptance criterion about webhook continuity via immutable ID, but the second stated deliverable—sweeping every documented install link, explicitly including the README's install link—is not shown in this diff.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 44 PR(s), 347 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.

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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Important

🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪

🔍 Gittensory is reviewing…

AI analysis is in progress. This comment will update when the review is complete.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing}

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-13 09:35:52 UTC}

3 files · 1 AI reviewer · no blockers · readiness 100/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review: This PR changes guardrail-protected path(s): src/services/subnet-interface.ts (matched src/services/**).

Review summary
Small, well-contained rename PR: updates the hardcoded PUBLIC_GITHUB_APP_SLUG constant from "gittensory-orb" to "loopover-orb" and the two tests that assert its value, matching the description that the GitHub App was renamed in-place on GitHub's side. The full file content confirms the constant is used consistently to build both the descriptor's slug and installUrl, so the change is internally coherent and both call sites (unit and integration tests) are updated together. This closes issue #4772 and is narrowly scoped, touching only the identity constant and its direct test assertions.

Nits — 7 non-blocking

• The PR description mentions webhook/OAuth callback URL changes made on GitHub's side, but nothing in the diff verifies these against any code-side config; if those URLs are ever hardcoded elsewhere in the codebase (not shown here), confirm they don't need updating too.
• Consider a follow-up issue/PR to track the deferred `PUBLIC_API_ORIGIN` flip and removal of the old OAuth callback URL, per the description.
• nit: `src/services/subnet-interface.ts:25` still tells maintainers to install the "Gittensory GitHub App" even though this PR says the public App was renamed to Loopover ORB, so either update that user-facing onboarding string or explain why the old product name is intentionally retained there.
• `src/services/subnet-interface.ts:25` could say `Maintainers: install the Loopover ORB GitHub App on a gittensor-registered repository.` to keep the descriptor’s onboarding copy aligned with the new slug.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#4772
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 347 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 347 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
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 is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 44 PR(s), 347 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.

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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-13 09:36:06 UTC}

3 files · 2 AI reviewers · no blockers · readiness 100/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review: This PR changes guardrail-protected path(s): src/services/subnet-interface.ts (matched src/services/**).

Review summary
Straightforward one-string rename of the hardcoded `PUBLIC_GITHUB_APP_SLUG` product-identity constant from `gittensory-orb` to `loopover-orb`, with the two tests that assert its value updated in lockstep. The PR description traces the GitHub-side rename (in-place App slug change, not a new registration) and explicitly justifies why other `gittensory-orb` references in the test suite and changelog are intentionally left alone. The diff is narrow, internally consistent, and closes the linked issue #4772 as a pure identity update with no behavioral surface beyond the constant and its two assertions.

Nits — 7 non-blocking

• The PR touches only the code-side slug; confirm the webhook/callback URL changes on GitHub's side (mentioned in the description) don't require any corresponding env/config update in this repo before merge.
• None beyond what's already done — the change is minimal and matches its stated scope.
• nit: src/services/subnet-interface.ts:25 still tells maintainers to install the "Gittensory GitHub App" even though the public slug now resolves to the renamed Loopover ORB app, so consider updating that user-facing onboarding text or documenting why the old product wording remains intentional.
• src/services/subnet-interface.ts:25: align the onboarding step with the renamed public app, for example `Maintainers: install the Loopover ORB GitHub App on a gittensor-registered repository.` if that is now the public-facing name.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	2 reviewers, synthesized
Linked issue	✅ Linked	#4772
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 347 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 347 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
Improvement	⚠️ ℹ️ None detected	risk: low · value: none — No structural-improvement signals were detected for this PR. LLM value judgment: minor — A single hardcoded product-identity string is renamed with matching test updates, correctly scoped to the one real code reference to the App slug.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 44 PR(s), 347 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.

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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-13 09:42:50 UTC}

3 files · 1 AI reviewer · no blockers · readiness 100/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review: This PR changes guardrail-protected path(s): src/services/subnet-interface.ts (matched src/services/**).

Review summary
Straightforward one-string rename of the hardcoded `PUBLIC_GITHUB_APP_SLUG` product-identity constant from `gittensory-orb` to `loopover-orb`, with the two tests that assert its value updated in lockstep. The PR description traces the GitHub-side rename (in-place App slug change, not a new registration) and explicitly justifies why other `gittensory-orb` references in the test suite and changelog are intentionally left alone. The diff is narrow, internally consistent, and closes the linked issue #4772 as a pure identity update with no behavioral surface beyond the constant and its two assertions.

Nits — 7 non-blocking

• The PR touches only the code-side slug; confirm the webhook/callback URL changes on GitHub's side (mentioned in the description) don't require any corresponding env/config update in this repo before merge.
• None beyond what's already done — the change is minimal and matches its stated scope.
• nit: src/services/subnet-interface.ts:25 still tells maintainers to install the "Gittensory GitHub App" even though the public slug now resolves to the renamed Loopover ORB app, so consider updating that user-facing onboarding text or documenting why the old product wording remains intentional.
• src/services/subnet-interface.ts:25: align the onboarding step with the renamed public app, for example `Maintainers: install the Loopover ORB GitHub App on a gittensor-registered repository.` if that is now the public-facing name.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#4772
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 347 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 347 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
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 is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 44 PR(s), 347 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.

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 Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review