refactor(extension): rename browser extension manifests and API origin to loopover#5509
Merged
Conversation
…n to loopover Renames both apps/gittensory-extension and apps/gittensory-miner-extension manifests' name/description/action.default_title, the maintainer overlay's default API origin (now the live api.loopover.ai custom-domain route on the same Worker), the built extension zip's filename/path, and the download link on the site's /extension page. Updates the .gitignore entry, the production smoke-test target, and a stale CI-comment reference in lockstep so nothing disagrees with the renamed artifact. Deliberately unchanged: directory names (apps/gittensory-extension/, apps/gittensory-miner-extension/ — npm-package-adjacent, deferred), the gts_ token wire-format prefix and GITTENSORY_SESSION_PATTERN identifier, the real jsonbored/gittensory GitHub repo-slug demo string, and the site's own domain/API-origin env vars (a separate, not-yet-cut-over concern). Closes #5329.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 6117066 | Commit Preview URL Branch Preview URL |
Jul 12 2026, 11:53 PM |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5509 +/- ##
=======================================
Coverage 94.75% 94.75%
=======================================
Files 565 565
Lines 44920 44920
Branches 14675 14675
=======================================
Hits 42565 42565
Misses 1621 1621
Partials 734 734
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renames both
apps/gittensory-extensionandapps/gittensory-miner-extensionmanifests'name/description/action.default_titlefields, the maintainer overlay's default API origin, the built extension zip's filename/path, and the download link on the site's/extensionpage — plus the.gitignoreentry, production smoke-test target, and a stale CI-comment reference, kept in lockstep so nothing disagrees with the renamed artifact.New API origin:
DEFAULT_API_ORIGINnow points athttps://api.loopover.ai(washttps://gittensory-api.aethereal.dev). This is a real, already-deployedcustom_domain: trueroute on the samegittensory-apiWorker (same binary/D1) as the old domain — not a placeholder — wired live in #4762/#5345. The extension's default is client-side and independently overridable via its options page, so this is a low-risk change distinct from (and doesn't touch) the server's ownPUBLIC_API_ORIGIN/PUBLIC_SITE_ORIGIN, which remain on the old domain pending a separate, not-yet-scheduled cutover.Deliberately unchanged (each tracked elsewhere or genuinely out of scope)
apps/gittensory-extension/,apps/gittensory-miner-extension/) — npm-package-adjacent paths, deferred to the package rename (itself currently blocked on re-planning against a new@loopovernpm org).gts_token wire-format prefix and theGITTENSORY_SESSION_PATTERNidentifier — a wire-format/internal-identifier contract, not brand prose.jsonbored/gittensoryGitHub repo-slug string used in a demo mockup.gittensory.aethereal.dev) andPUBLIC_API_ORIGIN/PUBLIC_SITE_ORIGIN— separate, not-yet-cut-over concern.Follow-up filed separately
Verification surfaced that both extensions' runtime UI (the injected overlay panel in
content.js, bothoptions.htmlpages, and the miner's toolbar badge inopportunity-badge.js) still literally renders "Gittensory" — outside this issue's 4 stated deliverables (manifests, API origin, build script, download link) but a real gap against the epic's broader goal. Filed as its own background task so it can become a small, focused follow-up rather than scope-creeping this PR.Test plan
build-extension.mjsruns successfully end-to-end, producingapps/gittensory-ui/public/downloads/loopover-extension.zipwith the correctly-renamed manifest inside.npm run test:cigate green (typecheck, coverage, engine-parity, mcp/miner builds+packs, UI lint/typecheck/test/build).npm audit --audit-level=moderate— 0 vulnerabilities.extension-auth,extension-content,miner-toolbar-badge— 18 tests) that no assertion depended on the old brand string or old zip filename, so no test edits were needed.packages/gittensory-miner/docs/env-reference.md(unrelated drift surfaced by rebasing onto a movedorigin/main— a new upstream env var reference needed a doc regen).gittensory-extension/gittensory-miner-extensionreference is a directory-path reference, correctly left alone per this issue's own stated boundaries.Closes #5329.