Problem: Two Chrome/browser extensions still carry the old brand end-to-end — in their manifests, in the hardcoded API origin the maintainer overlay talks to, and in the site's download flow and build tooling around them. Neither extension has a package.json, so the npm-package-rename work item structurally cannot reach them. apps/gittensory-extension/manifest.json names itself "Gittensory Maintainer Overlay," describes itself as "Private Gittensory pull request context on GitHub," sets action.default_title to "Gittensory," and lists the old brand's API subdomain in host_permissions. apps/gittensory-miner-extension/manifest.json names itself "Gittensory Miner Opportunity" with an action.default_title of "Gittensory Miner." apps/gittensory-extension/auth.js hardcodes that same old API subdomain as its default origin. Left alone, both extensions keep advertising the old brand to anyone who installs them, and the maintainer overlay keeps calling the old API origin no matter what the backend gets renamed to.
Area: Extensions / Frontend
Proposal: Rename the name, description, and action.default_title fields in both manifest.json files to the new brand, and update the DEFAULT_API_ORIGIN constant in apps/gittensory-extension/auth.js to point at the new brand's API origin. Update the site's extension download page and the zip-building script in the same pass, since both currently derive their filename/path from the old brand — otherwise the download link and the artifact it points to will disagree with the renamed manifests.
Deliverables:
- Updated manifest.json for both apps/gittensory-extension and apps/gittensory-miner-extension carrying the new brand name, description, and action title.
- apps/gittensory-extension/auth.js's DEFAULT_API_ORIGIN updated to the new API origin.
- scripts/build-extension.mjs producing its distributable zip under the new brand's filename/path.
- apps/gittensory-ui/src/routes/extension.tsx's download link updated to match the renamed artifact.
Acceptance criteria:
Test scenarios:
- Load both extensions unpacked in a Chromium-based browser and confirm the toolbar title and the extension-management page show the new name.
- Run the build script and confirm the produced zip's filename and its internal manifest both reflect the new brand.
- Exercise the maintainer overlay's auth flow against the new API origin and confirm it functions end-to-end.
Resources:
- apps/gittensory-extension/manifest.json
- apps/gittensory-extension/auth.js (DEFAULT_API_ORIGIN, line 1)
- apps/gittensory-miner-extension/manifest.json
- apps/gittensory-ui/src/routes/extension.tsx (around line 53)
- scripts/build-extension.mjs (around lines 6-8)
Boundaries:
- Neither extension has a package.json, so this is separate from and not covered by the npm-package-rename work item.
- Leave every reference to the separate gittensor network's own domain/name untouched.
Part of #4761.
Problem: Two Chrome/browser extensions still carry the old brand end-to-end — in their manifests, in the hardcoded API origin the maintainer overlay talks to, and in the site's download flow and build tooling around them. Neither extension has a package.json, so the npm-package-rename work item structurally cannot reach them. apps/gittensory-extension/manifest.json names itself "Gittensory Maintainer Overlay," describes itself as "Private Gittensory pull request context on GitHub," sets action.default_title to "Gittensory," and lists the old brand's API subdomain in host_permissions. apps/gittensory-miner-extension/manifest.json names itself "Gittensory Miner Opportunity" with an action.default_title of "Gittensory Miner." apps/gittensory-extension/auth.js hardcodes that same old API subdomain as its default origin. Left alone, both extensions keep advertising the old brand to anyone who installs them, and the maintainer overlay keeps calling the old API origin no matter what the backend gets renamed to.
Area: Extensions / Frontend
Proposal: Rename the name, description, and action.default_title fields in both manifest.json files to the new brand, and update the DEFAULT_API_ORIGIN constant in apps/gittensory-extension/auth.js to point at the new brand's API origin. Update the site's extension download page and the zip-building script in the same pass, since both currently derive their filename/path from the old brand — otherwise the download link and the artifact it points to will disagree with the renamed manifests.
Deliverables:
Acceptance criteria:
Test scenarios:
Resources:
Boundaries:
Part of #4761.