Skip to content

docs(review): rename gittensory prose to loopover in src/review (batch A) - #5883

Merged
JSONbored merged 1 commit into
mainfrom
rebrand/prose-review-a
Jul 14, 2026
Merged

docs(review): rename gittensory prose to loopover in src/review (batch A)#5883
JSONbored merged 1 commit into
mainfrom
rebrand/prose-review-a

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • Part of the gittensory→loopover rebrand (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705), phase 8b: rename brand-name prose in comments across src/review/** — the reviewbot→loopover convergence-port modules (adapters, alerts, auto-apply/auto-tune, content-lane primitives), cutover-gate, enrichment wiring, feature activation, and related modules. Comment-only, no behavior change.
  • Deliberately left untouched: the pre-rename GITTENSORY_LEGACY_* check-run name constants and their exact string values (check-names.ts), the 'gittensory-native' review_audit.source discriminator used across parity/outcomes tracking (a real DB column value, not prose — renaming it would desync new writes from historically-recorded rows), the x-gittensory-request-id header the engine sends to the REES enrichment service, and the ../config/gittensory-repo-focus-manifest import path (the module itself is still filed under its old name; renaming just the import string would break module resolution).

Scope

  • The PR title follows type(scope): short summary Conventional Commit format.
  • This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
  • This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
  • I linked a currently open issue this PR resolves — N/A, maintainer-authored rebrand-epic cleanup (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705), no linked-issue gate applies to owner PRs.

Validation

  • git diff --check
  • npm run actionlint (via npm run test:ci)
  • npm run typecheck (via npm run test:ci)
  • npm run test:coverage — full unsharded run, 100% green; comment-only diff, no coverable lines changed
  • npm run test:workers (via npm run test:ci)
  • npm run build:mcp (via npm run test:ci)
  • npm run test:mcp-pack (via npm run test:ci)
  • npm run ui:openapi:check (via npm run test:ci)
  • npm run ui:lint (via npm run test:ci)
  • npm run ui:typecheck (via npm run test:ci)
  • npm run ui:build (via npm run test:ci)
  • npm audit --audit-level=moderate
  • Full npm run test:ci gate run locally, exit 0

Safety

  • No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
  • Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
  • Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — N/A, no such changes.
  • API/OpenAPI/MCP behavior is updated and tested where needed. — N/A, comment-only, no behavior change.
  • UI changes use live API data or real empty/error/loading states. — N/A, no UI changes.
  • Visible UI changes include a UI Evidence section. — N/A, no UI changes.
  • Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs (none touched here).

Notes

…h A)

Rebrand cutover cleanup: update brand-name prose in comments across
28 src/review/**/*.ts files (adapters, alerts, auto-apply/tune,
content-lane primitives, cutover-gate, enrichment, feature
activation, and related wiring modules). Comment-only changes, no
behavior change.

Deliberate legacy references (the pre-rename GITTENSORY_LEGACY_*
check-run name constants, the 'gittensory-native' review_audit
source discriminator, the x-gittensory-request-id REES header, and
the gittensory-repo-focus-manifest module path) are left untouched.
@superagent-security

Copy link
Copy Markdown
Contributor

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

@JSONbored JSONbored self-assigned this Jul 14, 2026
@JSONbored
JSONbored merged commit 769ddf9 into main Jul 14, 2026
5 checks passed
@JSONbored
JSONbored deleted the rebrand/prose-review-a branch July 14, 2026 21:09
JSONbored added a commit that referenced this pull request Jul 14, 2026
PR #5883 renamed brand-name prose in src/review/guardrail-config.ts
and src/review/linked-issue-label-propagation.ts but not their
byte-identical twins under packages/loopover-engine/src/review/,
breaking scripts/check-engine-parity.ts on main. Aligns the engine
copies' comment text with the host copies. Also fixes a stale
finding-taxonomy.test.ts assertion that still expected the
pre-rename "gittensory://finding-taxonomy" MCP resource URI literal
(the constant itself was already correctly renamed by #5883; only
this test's hardcoded expectation had drifted).
@nghetienhiep nghetienhiep mentioned this pull request 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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant