You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gittensory's review engine (internally "ORB") has grown a broad, differentiated feature set — linked-issue gating, AI-scored improvement signals, a visual-capture/screenshot gate, one-shot review cadence, and a mature layered config-as-code system. That maturity is the basis for a product rename to LoopOver. The domain (loopover.ai) is already purchased and DNS is live on Cloudflare; nothing in code, infrastructure, or public-facing surfaces has changed yet.
This is a full rename — repo, packages, infrastructure, the GitHub App, self-host config conventions, environment variables, and the MCP tool surface all carry the old name today, and all of it is in scope. Nothing is deferred indefinitely; the work is sequenced into four steps so each one is safe before the next starts, and so nothing is left half-renamed.
Note on REBRAND-C6: research confirmed a GitHub App's installations and webhook deliveries are keyed by its immutable app/client ID, not its slug. Renaming the App does not require a new OAuth client, and existing self-host installations are unaffected. No separate issue is needed for this — it's called out here so the reasoning isn't lost.
How to use this issue
Work top-to-bottom by step. Step 1 items are independent and can start immediately. Step 2 items depend on Step 1 being stable. Step 3 items are all in scope but each has its own execution risk — read its Boundaries section before starting. Step 4 only starts once every deprecation window named in Steps 2–3 has actually elapsed.
Context
gittensory's review engine (internally "ORB") has grown a broad, differentiated feature set — linked-issue gating, AI-scored improvement signals, a visual-capture/screenshot gate, one-shot review cadence, and a mature layered config-as-code system. That maturity is the basis for a product rename to LoopOver. The domain (
loopover.ai) is already purchased and DNS is live on Cloudflare; nothing in code, infrastructure, or public-facing surfaces has changed yet.This is a full rename — repo, packages, infrastructure, the GitHub App, self-host config conventions, environment variables, and the MCP tool surface all carry the old name today, and all of it is in scope. Nothing is deferred indefinitely; the work is sequenced into four steps so each one is safe before the next starts, and so nothing is left half-renamed.
Scope summary
Note on REBRAND-C6: research confirmed a GitHub App's installations and webhook deliveries are keyed by its immutable app/client ID, not its slug. Renaming the App does not require a new OAuth client, and existing self-host installations are unaffected. No separate issue is needed for this — it's called out here so the reasoning isn't lost.
How to use this issue
Work top-to-bottom by step. Step 1 items are independent and can start immediately. Step 2 items depend on Step 1 being stable. Step 3 items are all in scope but each has its own execution risk — read its Boundaries section before starting. Step 4 only starts once every deprecation window named in Steps 2–3 has actually elapsed.