Context
The gittensory → loopover rebrand (epic #5705, closed completed 2026-07-14) renamed the CLI binaries, npm package directories, and Cloudflare Worker resource names, but four contributor-facing doc files still cite the pre-rename names/paths — none of these were mentioned in #5705's own status-update comments, so they slipped through:
CONTRIBUTING.md (lines ~251-263, "Cloudflare/deploy" section) still calls the production Workers gittensory-ui and gittensory-api. The actual "name" fields are now "loopover-ui" (apps/loopover-ui/wrangler.jsonc) and "loopover-api" (root wrangler.jsonc). A contributor looking up the Worker in the Cloudflare dashboard by the name CONTRIBUTING.md gives them won't find it.CONTRIBUTING.md line ~272 tells contributors to run gittensory-mcp init-client --print. That binary no longer exists — the package's actual bin entry (packages/loopover-mcp/package.json) is loopover-mcp.packages/loopover-miner/README.md has two broken relative markdown links that point at directories that no longer exist:
- line ~212:
[cli-subprocess-driver.ts](../gittensory-engine/src/miner/cli-subprocess-driver.ts) — should be ../loopover-engine/...
- line ~262:
[@loopover/mcp README](../gittensory-mcp/README.md#client-config) — should be ../loopover-mcp/README.md#client-config
(packages/gittensory-engine and packages/gittensory-mcp were both renamed to packages/loopover-engine / packages/loopover-mcp; verified via git ls-tree -r origin/main -- packages/ — no packages/gittensory-* path exists.)
.claude/skills/contributing-to-loopover/SKILL.md (lines ~100-102, ~276) and .claude/skills/contributing-to-loopover/reference.md (lines ~147-149) give contributors (and AI coding agents, including the one reading this very skill to write PRs) copy-pasteable commands using the dead gittensory-mcp binary name (gittensory-mcp login, gittensory-mcp init-client --print codex, etc.), and SKILL.md:276 still says "gittensory-ui is a dark-mode-only..." for the visual-review guidance.
None of these are speculative — every renamed target (loopover-mcp bin, loopover-ui/loopover-api Worker names, packages/loopover-engine/packages/loopover-mcp directories) already exists and is live on main; only the doc text lags.
Requirements
- Update
CONTRIBUTING.md's Cloudflare/deploy section to say loopover-ui and loopover-api (Worker names, deploy-command references, and any surrounding sentence that reads awkwardly after the substitution).
- Fix the
gittensory-mcp init-client --print command in CONTRIBUTING.md to loopover-mcp init-client --print.
- Fix both broken relative links in
packages/loopover-miner/README.md to point at the real packages/loopover-engine/... and packages/loopover-mcp/README.md#client-config paths.
- Fix every
gittensory-mcp command example in .claude/skills/contributing-to-loopover/SKILL.md and reference.md to loopover-mcp, and fix the gittensory-ui mention in SKILL.md's visual-review section to loopover-ui.
- Grep the four files above for any other stray
gittensory- string once these are fixed, to make sure nothing was missed in the same pass.
Deliverables
Test Coverage Requirements
Docs-only change (*.md files) — outside coverage.include (see codecov.yml: coverage is collected only over src/**, packages/loopover-engine/src/**, and packages/loopover-miner/lib/**). Codecov's patch/project gates will not fire on this PR; that's expected, not a sign anything was skipped.
Expected Outcome
A contributor following CONTRIBUTING.md or the contributing-to-loopover skill can copy-paste every CLI command and it actually runs; every relative link in the miner README resolves; no doc references a Worker or package name that no longer exists.
Links & Resources
Context
The
gittensory→loopoverrebrand (epic #5705, closed completed 2026-07-14) renamed the CLI binaries, npm package directories, and Cloudflare Worker resource names, but four contributor-facing doc files still cite the pre-rename names/paths — none of these were mentioned in #5705's own status-update comments, so they slipped through:CONTRIBUTING.md(lines ~251-263, "Cloudflare/deploy" section) still calls the production Workersgittensory-uiandgittensory-api. The actual"name"fields are now"loopover-ui"(apps/loopover-ui/wrangler.jsonc) and"loopover-api"(rootwrangler.jsonc). A contributor looking up the Worker in the Cloudflare dashboard by the name CONTRIBUTING.md gives them won't find it.CONTRIBUTING.mdline ~272 tells contributors to rungittensory-mcp init-client --print. That binary no longer exists — the package's actualbinentry (packages/loopover-mcp/package.json) isloopover-mcp.packages/loopover-miner/README.mdhas two broken relative markdown links that point at directories that no longer exist:[cli-subprocess-driver.ts](../gittensory-engine/src/miner/cli-subprocess-driver.ts)— should be../loopover-engine/...[@loopover/mcp README](../gittensory-mcp/README.md#client-config)— should be../loopover-mcp/README.md#client-config(
packages/gittensory-engineandpackages/gittensory-mcpwere both renamed topackages/loopover-engine/packages/loopover-mcp; verified viagit ls-tree -r origin/main -- packages/— nopackages/gittensory-*path exists.).claude/skills/contributing-to-loopover/SKILL.md(lines ~100-102, ~276) and.claude/skills/contributing-to-loopover/reference.md(lines ~147-149) give contributors (and AI coding agents, including the one reading this very skill to write PRs) copy-pasteable commands using the deadgittensory-mcpbinary name (gittensory-mcp login,gittensory-mcp init-client --print codex, etc.), and SKILL.md:276 still says "gittensory-ui is a dark-mode-only..." for the visual-review guidance.None of these are speculative — every renamed target (
loopover-mcpbin,loopover-ui/loopover-apiWorker names,packages/loopover-engine/packages/loopover-mcpdirectories) already exists and is live onmain; only the doc text lags.Requirements
CONTRIBUTING.md's Cloudflare/deploy section to sayloopover-uiandloopover-api(Worker names, deploy-command references, and any surrounding sentence that reads awkwardly after the substitution).gittensory-mcp init-client --printcommand inCONTRIBUTING.mdtoloopover-mcp init-client --print.packages/loopover-miner/README.mdto point at the realpackages/loopover-engine/...andpackages/loopover-mcp/README.md#client-configpaths.gittensory-mcpcommand example in.claude/skills/contributing-to-loopover/SKILL.mdandreference.mdtoloopover-mcp, and fix thegittensory-uimention in SKILL.md's visual-review section toloopover-ui.gittensory-string once these are fixed, to make sure nothing was missed in the same pass.Deliverables
CONTRIBUTING.md:gittensory-ui/gittensory-api→loopover-ui/loopover-api;gittensory-mcp→loopover-mcppackages/loopover-miner/README.md: both relative links fixed topackages/loopover-engine/packages/loopover-mcp.claude/skills/contributing-to-loopover/SKILL.md:gittensory-mcpcommands →loopover-mcp;gittensory-ui→loopover-ui.claude/skills/contributing-to-loopover/reference.md:gittensory-mcpcommands →loopover-mcpTest Coverage Requirements
Docs-only change (
*.mdfiles) — outsidecoverage.include(seecodecov.yml: coverage is collected only oversrc/**,packages/loopover-engine/src/**, andpackages/loopover-miner/lib/**). Codecov'spatch/projectgates will not fire on this PR; that's expected, not a sign anything was skipped.Expected Outcome
A contributor following CONTRIBUTING.md or the
contributing-to-loopoverskill can copy-paste every CLI command and it actually runs; every relative link in the miner README resolves; no doc references a Worker or package name that no longer exists.Links & Resources
apps/loopover-ui/wrangler.jsonc, rootwrangler.jsonc— source of truth for the live Worker names.packages/loopover-mcp/package.json— source of truth for the livebinname.