docs: rewrite marketing and docs copy for LoopOver

[JSONbored]

Summary

• Renames genuine brand-prose mentions of "gittensory" to "LoopOver" across the README, all 35 docs-site route pages, and the 4 community health files (CONTRIBUTING/SECURITY/SUPPORT/CODE_OF_CONDUCT).
• Deliberately leaves every not-yet-renamed technical identifier untouched: npm package names (@jsonbored/gittensory-*), the check-run names (Gittensory Orb Review Agent/Gittensory Context/Gittensory Gate), the bot's GitHub login (gittensory[bot]), the .gittensory.yml config filename, GITTENSORY_-prefixed env vars, the repo path, and the gittensory.aethereal.dev/gittensory-api.aethereal.dev domains -- each is tracked by its own separate rebrand issue, and renaming them in docs now would describe a system that doesn't exist yet.
• gittensor (no trailing Y, the permanent Bittensor SN74 subnet brand) is untouched everywhere -- verified via balanced before/after occurrence counts across the full diff.
• Adds a "Formerly Gittensory" continuity note near the top of the README.

Also fixes (found along the way)

Three docs pages (GitHub App configuration, maintainer install/trust guide, maintainer self-hosting) advertised installing a "shared managed-beta" GitHub App at a literal install URL for an App that was fully deleted earlier in this rebrand. Reframed as "currently paused, self-hosting is the only available path today, a new centrally hosted offering is planned for the future" rather than deleting the content outright, so it's ready to reactivate when that offering ships.

Test plan

• npm run typecheck
• Independent diff-level verification: every technical identifier's occurrence count is identical before/after (check-run names, bot login, npm packages, config filename, env vars, domains); gittensor (no-Y) count unchanged (6/6)
• Updated 2 pre-existing tests whose assertions targeted the now-intentionally-removed dead install checklist / old brand string (docs-github-app.test.ts, docs-beta-onboarding.test.ts)
• npm run ui:lint / ui:typecheck / ui:test / ui:build all green
• npm run docs:drift-check, manifest:drift-check, engine-parity:drift-check, command-reference:check all green
• Full test:ci gate green (one ai-summaries.test.ts timeout under local full-suite parallel load confirmed as a pre-existing, environment-load-dependent flake -- passes standalone in ~2.4s, unrelated to this diff)

Closes #4763.

[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	49eb96f	Commit Preview URL Branch Preview URL	Jul 12 2026, 03:39 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.39%. Comparing base (7935bb4) to head (49eb96f).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5376      +/-   ##
==========================================
- Coverage   94.43%   94.39%   -0.04%     
==========================================
  Files         551      551              
  Lines       44190    44190              
  Branches    14640    14640              
==========================================
- Hits        41731    41714      -17     
- Misses       1784     1801      +17     
  Partials      675      675              

Flag	Coverage Δ
shard-1	43.77% <ø> (-0.38%)	⬇️
shard-2	34.17% <ø> (-0.41%)	⬇️
shard-3	32.19% <ø> (+0.63%)	⬆️
shard-4	31.22% <ø> (-0.06%)	⬇️
shard-5	33.11% <ø> (-0.21%)	⬇️
shard-6	43.62% <ø> (+0.21%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

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

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-12 15:49:44 UTC}

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

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review: This PR changes guardrail-protected path(s): apps/gittensory-ui/src/routes/docs.ai-summaries.tsx (matched apps/gittensory-ui/**), apps/gittensory-ui/src/routes/docs.beta-onboarding.tsx (matched apps/gittensory-ui/**), apps/gittensory-ui/src/routes/docs.branch-analysis.tsx (matched apps/gittensory-ui/**), apps/gittensory-ui/src/routes/docs.github-app.tsx (matched apps/gittensory-ui/**), apps/gittensory-ui/src/routes/docs.gittensory-commands.tsx (matched apps/gittensory-ui/**), and 30 more.

Review summary
This is a large, mechanical brand-prose rewrite (Gittensory → LoopOver) across the README, 35 docs routes, and 4 community-health files, deliberately leaving every technical identifier (npm packages, check-run names, bot login, `.gittensory.yml`, `GITTENSORY_` env vars, domains) untouched per the description's stated scope. It also removes the now-stale shared managed-beta GitHub App install checklist/URL from docs.github-app.tsx, docs.maintainer-self-hosting.tsx, and docs.maintainer-install-trust.tsx, replacing it with an honest 'currently paused' callout rather than deleting the content outright — a reasonable, low-risk approach for content that's not yet reactivatable. Spot-checking several hunks against the full post-change file content shows consistent renames with no orphaned references to the removed `GITHUB_APP_INSTALL_URL` constant, and CI (typecheck/build/tests) is green on this exact commit.

Nits — 7 non-blocking

• docs.github-app.tsx:144 keeps the pre-existing 'master switch' phrasing — consider 'primary switch' or 'top-level switch' while you're touching this copy anyway.
• The PR's issue linkage to Rewrite marketing & docs copy for LoopOver #4763 is flagged as only partially covering that issue's scope — confirm the issue is fully closed by this PR or note what remains for a follow-up.
• Test-to-code ratio is very low (5 test lines for 35 source files), though for a pure copy/prose rewrite with green typecheck/build this is expected rather than a coverage gap.
• Double check for any remaining un-renamed brand-prose instances outside the shown hunks (e.g. grep the full repo for standalone 'Gittensory docs'/'Gittensory review' phrases) to make sure the rename is exhaustive across all 42 changed files, not just the ones shown here.
• Since docs.github-app.tsx removes the shared-App install checklist entirely, verify no other route or test still references the deleted `<ol>` steps or `GITHUB_APP_INSTALL_URL` by 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.
• 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	#4763
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High 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, 463 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 463 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
Improvement	✅ Minor	risk: clean · value: minor — Code changes are accompanied by test evidence.

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), 463 issue(s).
• Related work: Titles/paths share 3 meaningful terms. (issue #4763, issue #4767)
• Related work: Titles/paths share 3 meaningful terms. (issue #4763, issue #4801)
• Related work: Titles/paths share 3 meaningful terms. (issue #4763, issue #4803)

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Review top overlaps.
• Add a concise scope and risk note.
• Check active issues and PRs before submitting.

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
/docs/ai-summaries	desktop			—
/docs/ai-summaries	mobile			—
/docs/beta-onboarding	desktop			—
/docs/beta-onboarding	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