refactor(infra): rename gittensory-api/-ui Cloudflare Workers and D1 database to loopover

[JSONbored]

Summary

Note: the live Cloudflare-side Worker renames already happened (dashboard rename, both gittensory-api -> loopover-api and gittensory-ui -> loopover-ui) — this PR syncs the code side to match, which is required before the next push to main or Workers Builds' auto-deploy will fail (its git integration requires the dashboard-registered Worker name and wrangler.jsonc's name field to agree).

• wrangler.jsonc / apps/gittensory-ui/wrangler.jsonc: name field updated to match the already-renamed live Workers. This was a genuine in-place rename of the existing resources (same script identity, bindings, routes) — not a provision-new-and-cutover.
• wrangler.jsonc's D1 binding: database_name relabeled gittensory -> loopover, same database_id (the immutable UUID Cloudflare actually uses to resolve the binding). Confirmed via wrangler deploy --dry-run that this label has zero effect on which physical database gets bound — not a data migration: no rows moved, no export/import, zero downtime. There's no known Cloudflare API to rename the D1 database record itself, so the Cloudflare-side record keeps its own registered name; only the code-side reference changes.
• .github/workflows/ui-preview-deploy.yml: fixed hardcoded "gittensory-ui" references (the trusted preview wrangler config's name field, and the grep pattern that locates the deployed preview's workers.dev URL in wrangler's output) — both would have broken the next PR preview deploy now that the live rename has landed.

Test plan

• wrangler deploy --dry-run on both Workers — clean, bindings resolve correctly under the new names.
• Full npm run test:ci gate green (one transient, unrelated flake in miner-attempt-worktree.test.ts — a known temp-git-repo signing-gate timing issue, confirmed by re-running in isolation).
• Repo-wide sweep for any other functional (non-directory-path) reference to the old Worker script names — only ui-preview-deploy.yml had real hits, now fixed.

Closes #4766. Closes #4767 (via the database_name relabel described above — no data migration was required or attempted, since Cloudflare D1's binding resolves by immutable UUID, not by this human-readable label).

[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	loopover-ui	e576ded	Commit Preview URL Branch Preview URL	Jul 13 2026, 06:12 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.96%. Comparing base (0798d02) to head (e576ded).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5569   +/-   ##
=======================================
  Coverage   94.96%   94.96%           
=======================================
  Files         572      572           
  Lines       45370    45370           
  Branches    14680    14680           
=======================================
  Hits        43087    43087           
  Misses       1532     1532           
  Partials      751      751           

Flag	Coverage Δ
shard-1	44.12% <ø> (ø)
shard-2	35.72% <ø> (ø)
shard-3	32.16% <ø> (ø)
shard-4	32.92% <ø> (ø)
shard-5	31.88% <ø> (+<0.01%)	⬆️
shard-6	43.90% <ø> (ø)

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]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-13 06:16:33 UTC}

3 files · 2 AI reviewers · 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/wrangler.jsonc (matched **/wrangler.jsonc), apps/gittensory-ui/wrangler.jsonc (matched apps/gittensory-ui/**), .github/workflows/ui-preview-deploy.yml (matched .github/workflows/**), wrangler.jsonc (matched wrangler.jsonc), wrangler.jsonc (matched **/wrangler.jsonc).

Review summary
This is a narrow, well-scoped rename of the `wrangler.jsonc` `name` fields (gittensory-api/-ui -> loopover-api/-ui) and the D1 `database_name` label to match an already-completed Cloudflare dashboard rename, plus fixing the two hardcoded `gittensory-ui` references in the preview-deploy workflow (config name and the URL-matching grep) that would otherwise break the next PR preview deploy. The D1 change is correctly just a label relabel with the same `database_id`, so it carries no data-migration risk as described. The diff matches its stated intent precisely and CI is green on this exact commit.

Nits — 7 non-blocking

• CONTRIBUTING.md's Cloudflare/deploy section still says 'Production UI deploys through the `gittensory-ui` Cloudflare Worker' and references the `gittensory-api` worker by name — those are now stale worker-script names post-rename and should be updated in this PR or a fast follow-up.
• The PR description doesn't include an explicit 'Closes #NNNN' — confirm it links the authorizing issue (the external brief references Rename Cloudflare Worker services #4766 'Rename Cloudflare Worker services') per this repo's issue-linking requirement for contributor PRs.
• Since `wrangler.jsonc`'s full content wasn't shown, worth double-checking there are no service-binding references elsewhere in that file pointing at the old `gittensory-api`/`gittensory-ui` script names, which would need the same rename.
• Add the closing issue reference to the PR description if not already present, since this repo requires every PR to close/link an eligible issue.
• Update CONTRIBUTING.md's deploy section to reference the new `loopover-api`/`loopover-ui` worker names for consistency with the renamed resources.
• 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	2 reviewers, synthesized
Linked issue	✅ Linked	#4766, #4767
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 (2 linked issues).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 379 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 379 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.
Improvement	⚠️ ℹ️ Insufficient signal	risk: clean · value: insufficient-signal — Nothing measurable for the structural-improvement analyzers on this PR (e.g. no code files changed). LLM value judgment: moderate — This is necessary, narrowly-targeted infra housekeeping that prevents the next push to main from breaking Workers Builds auto-deploy and the PR preview pipeline, following through on an already-completed dashboard-side rename.

Linked issue satisfaction

Partially addressed
The PR explicitly takes an in-place rename approach (dashboard rename + config sync) rather than the issue's requested provision-new-Worker/cutover/verification-window strategy, so the deliverables and acceptance criteria around zero-error cutover and pre-cutover binding verification on separate new services are not applicable/fulfilled as specified; bindings are confirmed unchanged via dry-run, b

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: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 44 PR(s), 379 issue(s).
• Related work: Titles/paths share 4 meaningful terms. (issue #4767, issue #4774)
• Related work: Titles/paths share 3 meaningful terms. (issue #5119, issue #4767)
• Related work: Titles/paths share 3 meaningful terms. (issue #5120, issue #4767)
• Additional title-only matches omitted; title-only overlap does not block.

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
/	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