refactor(extension): rename remaining Gittensory brand-prose in runtime UI

[JSONbored]

Summary

Renames the literal display text (visible labels, aria-labels, page titles, headings, body copy) in the maintainer overlay's injected panel and options page, and the miner extension's opportunity badge and options page, from "Gittensory" to "LoopOver" — these were the on-page text a user actually sees, left untouched by #5329's own literal deliverables (manifests, API origin, build script, download link).

Deliberately unchanged

• CSS class names and dataset attributes (gittensory-overlay__*, data-gittensory-pr-context, etc.) — internal identifiers, not brand-prose, matching the existing convention (see auth.js's GITTENSORY_SESSION_PATTERN).
• The real apps/gittensory-extension/ directory-path reference in the miner options page's body copy.

Test plan

• Full npm run test:ci gate green.
• Fixed the one test assertion (miner-extension-content.test.ts) that checked the renamed badge text.

Closes #5533.

[superagent-security]

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

[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	gittensory-ui	564fc9c	Commit Preview URL Branch Preview URL	Jul 13 2026, 02:46 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.79%. Comparing base (ff94e35) to head (564fc9c).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5535   +/-   ##
=======================================
  Coverage   94.79%   94.79%           
=======================================
  Files         566      566           
  Lines       45065    45065           
  Branches    14675    14675           
=======================================
  Hits        42718    42718           
  Misses       1613     1613           
  Partials      734      734           

Flag	Coverage Δ
shard-1	43.65% <ø> (-0.56%)	⬇️
shard-2	35.53% <ø> (+0.06%)	⬆️
shard-3	32.11% <ø> (+0.16%)	⬆️
shard-4	31.35% <ø> (-0.58%)	⬇️
shard-5	33.32% <ø> (+0.45%)	⬆️
shard-6	43.72% <ø> (+0.20%)	⬆️

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

🚀 New features to boost your workflow:

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

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ Gittensory review result - approve/merge recommended

_{Review updated: 2026-07-13 02:50:26 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a narrow, mechanical rename of user-visible brand text ("Gittensory" → "LoopOver") in the maintainer overlay and miner extension's HTML titles, headings, body copy, and injected DOM markup, plus the corresponding test assertion update. It correctly follows the stated scope by leaving CSS classes, dataset attributes, and directory-path references untouched, matching the PR's own convention note. The diff is small, self-contained, and closes issue #5533 as required.

Nits — 7 non-blocking

• The renamed aria-label in apps/gittensory-extension/content.js:33 ("Refresh LoopOver context") and the badge text in opportunity-badge.js:85 are only covered by the single test assertion updated in miner-extension-content.test.ts — the maintainer overlay's own aria-label/header text has no direct assertion in the visible test files, though this may be covered elsewhere not shown in the diff.
• Verify there isn't an existing extension test (not shown in this diff) asserting the maintainer overlay's header text or aria-label that also needs the rename, e.g. a content.js-focused test file.
• nit: apps/gittensory-extension/content.js:29 and apps/gittensory-miner-extension/opportunity-badge.js:84 still render a visible `G` mark, so either change that visible mark to `L` or state explicitly that the mark is a logo asset rather than brand prose.
• nit: test/unit/miner-extension-content.test.ts:97 only covers the miner badge rename; the maintainer overlay header/aria-label and both options-page titles/headings/body copy remain unasserted.
• nit: apps/gittensory-miner-extension/options.html:57 keeps the implementation path in body copy as intended, but this is easy to confuse with missed prose later, so a short HTML comment would make the exception self-documenting.
• 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.

Signal	Result	Evidence
Code review	✅ No blockers	2 reviewers, synthesized
Linked issue	✅ Linked	#5533
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, 403 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 403 issue(s).
Gate result	✅ Passing	No configured blocker found.
Improvement	⚠️ ℹ️ None detected	risk: low · value: none — No structural-improvement signals were detected for this PR. LLM value judgment: minor — This is a straightforward, low-risk brand-text cleanup that completes a rename left incomplete by a prior PR, with no functional or architectural impact.

Linked issue satisfaction

Addressed
The diff renames all four cited brand-prose locations (content.js overlay label and aria-label, both options.html titles/headings/body copy, and opportunity-badge.js label) to LoopOver while correctly leaving CSS class names, dataset attributes, and the directory-path reference untouched, matching the issue's acceptance criteria and boundaries.

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), 403 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

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/	desktop			—
/	mobile			—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

_{🟩 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]

Gittensory approves — the gate is satisfied and CI is green.