Skip to content

fix(rebrand): full-cutover rename remaining internal gittensory runtime identifiers - #5761

Merged
JSONbored merged 1 commit into
mainfrom
rebrand-phase8-runtime
Jul 14, 2026
Merged

fix(rebrand): full-cutover rename remaining internal gittensory runtime identifiers#5761
JSONbored merged 1 commit into
mainfrom
rebrand-phase8-runtime

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • Rebrand epic Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705, Phase 8a: renames functional runtime identifiers that survived Phases 1-7 because they weren't caught by prior sed/perl sweeps — bare positional-argument audit-actor strings, Sentry allowed-context/fingerprint/monitor-slug names, OTel default service name + span attributes, HKDF/hash namespace strings, the miner's worktree branch-prefix/subdir constants, and the browser-extension message-passing protocol strings + CSS class names.
  • Fixes a real regression: apps/loopover-extension/content.js's duplicate-mount guard was querying the pre-Phase-6 attribute name after the setter was renamed, silently disabling the guard.
  • Fixes stale generated doc drift in packages/loopover-miner/docs/env-reference.md (title never regenerated after Phase 5 fixed the generator).
  • Finishes an incomplete earlier rename: apps/loopover-ui's /docs/gittensory-commands route (file + URL + footer/nav links) was left stale even though the @gittensory@loopover mention-command docs it covers were already renamed in Phase 2 — every bot comment footer was linking to a URL that no longer matched the feature name.

Deliberately not touched (confirmed permanent/deferred):

  • The real, unrenamed JSONbored/gittensory GitHub repo and Sentry-project references
  • GITTENSORY_LEGACY_* check-run constants
  • The already-decided gittensory-selfhost container-image legacy alias
  • PUBLIC_SITE_ORIGIN_ALIASES domain alias
  • .gittensory-miner.yml per-repo config filename — a large (37-file), distinct surface, deferred to its own follow-up PR

Test plan

  • npm run typecheck clean
  • npx vitest run — 837 files / 16251 tests passed (2 pre-existing skips)
  • full npm run test:ci gate green end-to-end (migrations, schema-drift, env-reference, actionlint, engine/mcp/miner builds+packs, docs/manifest/engine-parity drift, UI lint/typecheck/test/build)
  • regenerated apps/loopover-ui/public/openapi.json and routeTree.gen.ts after source changes

…me identifiers

Phase 8a of the rebrand epic (#5705): renames functional runtime
identifiers that survived Phases 1-7 because they weren't caught by
prior sed/perl sweeps (bare positional-argument actor strings, object
keys, Sentry context/fingerprint names, OTel span attributes, HKDF/hash
namespace strings, extension message-passing protocol strings and CSS
class names, and the miner's worktree branch prefix/subdir).

Also fixes two regressions/drift discovered along the way:
- apps/loopover-extension/content.js's data-attribute duplicate-mount
  guard was querying the old gittensory-prefixed attribute name after
  Phase 6 renamed the setter, silently disabling the guard.
- packages/loopover-miner/docs/env-reference.md's checked-in title was
  stale against its Phase-5-fixed generator.
- apps/loopover-ui's docs.gittensory-commands.tsx route file (and its
  footer/nav links) were never renamed even though the @Loopover
  mention-command docs it covers already were (Phase 2), leaving a
  stale /docs/gittensory-commands URL in every bot comment footer.

Deliberately NOT touched: the real (unrenamed) JSONbored/gittensory
GitHub/Sentry-project references, GITTENSORY_LEGACY_* check-run
constants, the already-decided gittensory-selfhost container-image
legacy alias, the PUBLIC_SITE_ORIGIN_ALIASES domain alias, and the
.gittensory-miner.yml per-repo config filename (separate, large,
deferred to its own follow-up).
@superagent-security

Copy link
Copy Markdown
Contributor

Superagent didn't find any vulnerabilities or security issues in this PR.

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.07%. Comparing base (9a19dff) to head (2b48186).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5761   +/-   ##
=======================================
  Coverage   95.07%   95.07%           
=======================================
  Files         581      581           
  Lines       46181    46181           
  Branches    14811    14811           
=======================================
  Hits        43905    43905           
  Misses       1516     1516           
  Partials      760      760           
Flag Coverage Δ
shard-1 43.95% <80.76%> (ø)
shard-2 35.74% <46.15%> (ø)
shard-3 32.27% <57.69%> (ø)
shard-4 32.95% <42.30%> (ø)
shard-5 31.76% <34.61%> (-0.01%) ⬇️
shard-6 44.64% <57.69%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...ackages/loopover-engine/src/miner/worktree-plan.ts 100.00% <100.00%> (ø)
src/db/repositories.ts 96.71% <100.00%> (ø)
src/github/client.ts 100.00% <ø> (ø)
src/github/e2e-test-commit.ts 100.00% <100.00%> (ø)
src/github/footer.ts 100.00% <100.00%> (ø)
src/github/repo-doc-pr.ts 100.00% <100.00%> (ø)
src/openapi/spec.ts 99.42% <ø> (ø)
src/queue/dlq.ts 100.00% <ø> (ø)
src/queue/processors.ts 95.67% <ø> (ø)
src/queue/review-evasion.ts 100.00% <ø> (ø)
... and 14 more
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@JSONbored
JSONbored merged commit 75450f1 into main Jul 14, 2026
19 checks passed
@JSONbored
JSONbored deleted the rebrand-phase8-runtime branch July 14, 2026 12:48
@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 14, 2026
This was referenced Jul 14, 2026
This was referenced Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant