diff --git a/packages/loopover-engine/README.md b/packages/loopover-engine/README.md index 45e4f3ff37..3b3ca7d56a 100644 --- a/packages/loopover-engine/README.md +++ b/packages/loopover-engine/README.md @@ -1,6 +1,6 @@ # @loopover/engine -Shared, deterministic engine logic for the LoopOver review stack and the `gittensory-miner`. +Shared, deterministic engine logic for the LoopOver review stack and the `loopover-miner`. This package houses pure, side-effect-free logic (scoring preview/model, predicted-gate types, reward-risk, slop signals, focus-manifest parse/compile core, duplicate-winner adjudication, and their engine-parity diff --git a/packages/loopover-mcp/README.md b/packages/loopover-mcp/README.md index 2d28d29bde..7ba527b7db 100644 --- a/packages/loopover-mcp/README.md +++ b/packages/loopover-mcp/README.md @@ -129,7 +129,7 @@ loopover-mcp analyze-branch --login jsonbored \ ## Review your PR locally before you push `loopover-mcp review-pr` composes the existing preflight, slop-risk, and PR-text-lint checks into -ONE report, so your own local agent (Claude Code, Codex, etc.) can see everything the gittensory gate +ONE report, so your own local agent (Claude Code, Codex, etc.) can see everything the loopover gate would flag before you ever open a PR. It is a thin composition layer — it calls the same checks `preflight`, `slop-risk`, and `lint-pr-text` already run and merges their output; it does not reimplement any of them. diff --git a/packages/loopover-ui-kit/src/theme.css b/packages/loopover-ui-kit/src/theme.css index fe48db6caf..0ea706932d 100644 --- a/packages/loopover-ui-kit/src/theme.css +++ b/packages/loopover-ui-kit/src/theme.css @@ -1,7 +1,7 @@ /* - * Gittensory design system — shared tokens + base layer. + * LoopOver design system — shared tokens + base layer. * Extracted from apps/loopover-ui/src/styles.css so every consuming app - * (gittensory-ui, gittensory-miner-ui) renders from one source of truth. + * (loopover-ui, loopover-miner-ui) renders from one source of truth. * Palette: Lovable Lime — AA-tuned citron/lime (#c4f24c family), light + dark * are first-class, toggled via .dark on documentElement. All colors in oklch. * Fonts: Space Grotesk (headings) + DM Sans (body) + JetBrains Mono (code). @@ -291,8 +291,8 @@ } } -/* Shared focus + hover utilities — generic enough that both gittensory-ui - and gittensory-miner-ui use them directly, unlike the hero/marketing-only +/* Shared focus + hover utilities — generic enough that both loopover-ui + and loopover-miner-ui use them directly, unlike the hero/marketing-only flourishes (aurora-glow, bg-grid, gradient-border) that stay app-local. */ @layer utilities { .focus-ring { diff --git a/review-enrichment/Dockerfile b/review-enrichment/Dockerfile index 6e68312fb1..7bef6a95b9 100644 --- a/review-enrichment/Dockerfile +++ b/review-enrichment/Dockerfile @@ -1,4 +1,4 @@ -# Gittensory review-enrichment service (REES). Lean two-stage Node build; analyzers are pure-JS diff-hunk +# LoopOver review-enrichment service (REES). Lean two-stage Node build; analyzers are pure-JS diff-hunk # heuristics with no external CLI tools (#1477 scoped this to the cheap, no-checkout path -- see # review-enrichment/src/analyzers/complexity.ts's header for why a real linter/AST toolchain is out of scope). # Build context = the review-enrichment/ directory (Railway "Root Directory" = review-enrichment). diff --git a/review-enrichment/README.md b/review-enrichment/README.md index d964c98962..0c240b3819 100644 --- a/review-enrichment/README.md +++ b/review-enrichment/README.md @@ -1,6 +1,6 @@ # Review-enrichment service (REES) -A standalone microservice that produces a structured **review brief** for the gittensory review engine. Run it +A standalone microservice that produces a structured **review brief** for the loopover review engine. Run it in-network alongside a self-hosted engine via the repo-root `docker-compose --profile rees` service (the simplest path, no separate hosting to manage — see the [self-hosting REES docs](https://loopover.ai/docs/self-hosting-rees)), or deploy it as its own service on any platform that can run a Dockerfile-based Node service — see @@ -247,7 +247,7 @@ Set these Railway service variables: | `SENTRY_TRACES_SAMPLE_RATE` | Optional; defaults to `0`, so errors report without tracing. | | `SENTRY_RELEASE` | Optional override. Only set it when that exact REES bundle is uploaded. | | `SENTRY_URL` | Optional Sentry API URL; defaults to `https://sentry.io`. | -| `SENTRY_REPOSITORY` | Optional; defaults to `JSONbored/gittensory` for commit association. | +| `SENTRY_REPOSITORY` | Optional; defaults to `JSONbored/loopover` for commit association. | | `REES_SENTRY_UPLOAD_STRICT` | Optional. Set `true` to fail startup if source-map upload fails. | | `REES_SENTRY_VALIDATE_RELEASE` | Optional. Set `false` only to disable post-upload release validation. | @@ -296,7 +296,7 @@ Useful production queries: - `event:rees_route_error route:/v1/enrich method:POST` - Analyzer failures grouped by analyzer: - `event:rees_analyzer_degraded analyzer:history` - - `event:rees_analyzer_degraded analyzer:dependency repo:JSONbored/gittensory` + - `event:rees_analyzer_degraded analyzer:dependency repo:JSONbored/loopover` - Source-map upload/startup failures on a Railway deploy: - `event:rees_sourcemap_upload_failed railwayDeploymentId:` - Process-level crashes: diff --git a/src/review/repo-agnostic-capability-audit.md b/src/review/repo-agnostic-capability-audit.md index 34db8ce8c7..2cbfd0a6c6 100644 --- a/src/review/repo-agnostic-capability-audit.md +++ b/src/review/repo-agnostic-capability-audit.md @@ -115,8 +115,8 @@ is a generic role vocabulary, not a gittensory assumption — no change needed. | Location | Assumption | Category | Should become | | --- | --- | --- | --- | -| `maintainer-recap-wire.ts:203` | `actor: "gittensory"` | (7) branding | Per-tenant actor identity string. | -| `parity.ts:254`, `stats.ts:112`, `parity-wire.ts:218` | shadow-writer default `"gittensory"` (parity self-join compares `reviewbot` vs `gittensory`) | (7) branding | Per-tenant shadow-writer name; the parity comparison is otherwise generic. | +| `maintainer-recap-wire.ts:203` | `actor: "loopover"` | (7) branding | Per-tenant actor identity string. | +| `parity.ts:254`, `stats.ts:112` | shadow-writer default `"loopover"` (parity self-join compares `reviewbot` vs `loopover`) | (7) branding | Per-tenant shadow-writer name; the parity comparison is otherwise generic. (`parity-wire.ts:218`'s `computeParityReadiness` deliberately overrides this default to the preserved `gittensory-native` DB-source literal instead -- a historical-compat value, not a per-tenant branding default.) | ### `src/review/check-names.ts` and `src/review/unified-comment*.ts` — check-run + comment branding @@ -138,8 +138,8 @@ These were checked and are already tenant-agnostic / config-driven; call them ou implementation issue doesn't redo them: - **`src/rules/` gate logic** — `predicted-gate.ts` re-exports the engine's `predicted-gate.js` wholesale, - and `advisory.ts` contains only generic gate-decision logic (the `gittensory`/`loopover` mentions at - `advisory.ts:563/895/911/945` are explanatory comments, not hardcoded identity). The rules layer is + and `advisory.ts` contains only generic gate-decision logic (the `loopover` mentions at + `advisory.ts:580/919/935/969` are explanatory comments, not hardcoded identity). The rules layer is already repo-agnostic. - **Label propagation** — `linked-issue-label-propagation.ts` / `-fetch.ts` drive their mappings from a configurable `linkedIssueLabelPropagation` setting (`DEFAULT_LINKED_ISSUE_LABEL_PROPAGATION` fallback); @@ -150,7 +150,7 @@ implementation issue doesn't redo them: (the finding above), not the mechanism. - **Signals maintainer-lane / role model** — `signals/engine.ts:1642` uses a generic forge role vocabulary (`owner`/`org_member`/`collaborator`/`repo_maintainer`), not gittensory-specific roles. -- **`cutover-gate.ts` repo list** — the `"JSONbored/gittensory,..."` string at `cutover-gate.ts:8` is a +- **`cutover-gate.ts` repo list** — the `"JSONbored/loopover,..."` string at `cutover-gate.ts:8` is a comment example of the `owner/repo` env format; the actual list is env-supplied, not hardcoded. ## Prioritized checklist for the follow-up implementation issue