Rename the missing 6th npm workspace package (gittensory-ui-kit) and the standalone review-enrichment service

[JSONbored]

Problem: Issue #4769 ("Rename npm workspace packages") states there are five workspace packages needing renaming: engine, MCP, miner, UI, miner UI. The actual count under the apps/* + packages/* workspace glob is six — the missing one is packages/gittensory-ui-kit/package.json (@jsonbored/gittensory-ui-kit, "Shared design-system tokens and component primitives for gittensory-ui and gittensory-miner-ui"). The count is six and not eight because two of the four apps/* directories (gittensory-extension, gittensory-miner-extension) are browser extensions with only a manifest.json — no package.json, so npm workspaces never picks them up. Unlike apps/gittensory-ui and apps/gittensory-miner-ui, which are both private: true and never published, gittensory-ui-kit carries publishConfig.access: "public" — the same as the other three packages/* packages (engine, MCP, miner), but unlike the two private apps, its name is user-facing in a way the apps aren't. It's imported across roughly 53 files: 49 in apps/gittensory-ui/src (46 under src/components/ui/*.tsx, plus src/hooks/use-mobile.tsx, src/lib/utils.ts, and src/styles.css) and 4 in apps/gittensory-miner-ui/src (3 under src/routes/*.tsx, plus src/styles.css), all via @jsonbored/gittensory-ui-kit/* import paths — it's also declared as a direct dependency in both apps' package.json manifests.

Separately, review-enrichment/package.json (gittensory-review-enrichment, the standalone REES service, see #1473) sits outside the apps/* + packages/* workspaces glob entirely — the root package.json's workspaces field is exactly ["apps/*", "packages/*"]. It's installed independently via the root rees:install script (npm ci --prefix review-enrichment, bypassing npm workspace linking). Today gittensory runs it in-network via the self-hosted rees service defined in the root docker-compose.yml (started with docker compose --profile rees up -d) — that's the actual production path. It's also documented as deployable as its own standalone Dockerfile-based service on a platform like Railway, but gittensory's own Railway project for it was decommissioned and its railway.json was removed from this repo — no committed railway.json exists here today. Because #4769 frames its scope as "workspace packages," this service could be silently skipped even though it's a real npm-manifest-bearing service that still carries the old brand name in its package name, its README, and its Sentry release-id prefix (gittensory-rees@<commit-sha>).

Area: Infra / Naming

Proposal: Rename packages/gittensory-ui-kit's package name, directory, and keywords entry, and update its publishConfig metadata consistently with the new brand — since this package is genuinely intended for public npm distribution like the other three packages/* packages, its new name needs to be settled as part of the same package-naming decision covering the other five. Update all ~53 consuming import sites across apps/gittensory-ui/src and apps/gittensory-miner-ui/src to the new import path, and update both apps' package.json dependency declarations to match. Separately, rename review-enrichment/package.json's package name and brand references in its own README (including the Sentry release-id prefix) — the root rees:install/rees:test/etc. scripts only reference the review-enrichment directory path, not the package name, so they need no changes as long as the directory itself isn't renamed. Because this service's actual current deploy path is the self-hosted rees docker-compose service, verify that service still builds and reaches /ready under the new name before considering this done; the README's Railway section should also be updated for brand consistency, but since no railway.json currently exists in this repo, there's nothing to rename there.

Deliverables:

• packages/gittensory-ui-kit renamed (package name, directory, keywords, publish metadata) and all ~53 consuming import paths and both apps' package.json dependency entries updated in apps/gittensory-ui and apps/gittensory-miner-ui.
• review-enrichment/package.json renamed along with its README brand references (including the Sentry release-id prefix), with confirmation that the root rees:* scripts need no changes since they only reference the unchanged directory path.
• Confirmation that the self-hosted rees docker-compose service still builds and starts correctly under the new name.

Acceptance criteria:

• packages/gittensory-ui-kit is renamed everywhere, including its publishConfig metadata, with zero remaining old-brand import paths or dependency entries in apps/gittensory-ui or apps/gittensory-miner-ui.
• review-enrichment/package.json and its README brand references are renamed, and the self-hosted rees docker-compose service is verified working under the new name.

Test scenarios:

• Build apps/gittensory-ui and apps/gittensory-miner-ui after the import-path and dependency rename and confirm no unresolved module errors.
• Run review-enrichment's own build/test pipeline (npm run rees:test, which installs outside npm workspace linking via --prefix) to confirm the rename didn't break it, and run docker compose --profile rees up -d to confirm the self-hosted service still builds and passes its /ready healthcheck under the new name.

Resources:

• packages/gittensory-ui-kit/package.json
• review-enrichment/package.json and review-enrichment/README.md
• Root package.json (workspaces field, rees:install script)
• Root docker-compose.yml (rees service definition)

Boundaries:

• Leave every reference to the separate gittensor network's own domain/name untouched.
• review-enrichment sits outside the apps/* + packages/* workspace glob, so it is easy to miss when scoping this work as "workspace packages" — it must be treated as in-scope here explicitly, not skipped.
• Do not rename the review-enrichment directory itself, and do not add a new railway.json — the prior one was deliberately removed when gittensory's own Railway deployment was decommissioned in favor of self-hosting.
• Leave SENTRY_REPOSITORY's default value of the GitHub repo slug (JSONbored/gittensory) untouched here — that's the actual current repo name, and renaming it is scoped to the separate repo-rename issue (GitHub repo rename / gittensor repo update #4771), not this one.

---

Part of #4761.

[linear-code]

JSO-3788

[JSONbored]

Update: dedicated loopover npm org confirmed — target names corrected, execution deferred.

Same correction as #4769: the rename target is not @jsonbored/loopover-*. With the new dedicated loopover npm org, this issue's two packages become:

• @loopover/ui-kit (not @jsonbored/loopover-ui-kit)
• @loopover/rees (not @jsonbored/loopover-review-enrichment — the service is already called REES everywhere else in this codebase; the package name should match, not carry the old review-enrichment long-form name forward)

Also correcting an inconsistency in this issue's own original text: the Proposal said to rename packages/gittensory-ui-kit's directory, while the Boundaries section said the opposite for review-enrichment ("do not rename the directory"). Neither package's on-disk directory should be renamed as part of this work — that's the same deliberately-deferred decision noted across every package in this milestone (renaming directories cascades into ~100+ CI path-filter references and is its own separate call). Only the npm-published package name field and internal import paths change.

An initial attempt (PR #5391) used the wrong scope before this was caught, and has been closed rather than reworked in place. Like #4769, this needs the new org's publish access actually confirmed, and should land together with the other five packages in one coordinated pass — deferred for now in favor of easier, lower-risk items elsewhere in the milestone.

---

Part of #4761.