docs(packages): fix stale gittensory prose and audit citations

[JSONbored]

Summary

• Continues the repo-wide gittensory -> loopover rebrand cleanup sweep. Fixes self-referential prose in packages/loopover-engine/README.md, packages/loopover-mcp/README.md, packages/loopover-ui-kit/src/theme.css, and review-enrichment/Dockerfile/README.md describing loopover's own current gate/design-system/review-engine identity, plus a review-enrichment/README.md SENTRY_REPOSITORY default that had drifted from the real current default in review-enrichment/src/upload-sourcemaps.ts (verified: JSONbored/loopover, not JSONbored/gittensory).
• Re-verifies and fixes four citations in src/review/repo-agnostic-capability-audit.md that had gone stale since the audit was written, each checked directly against the real current source line:
  • maintainer-recap-wire.ts:203's actor is now "loopover", not "gittensory".
  • parity.ts/stats.ts's shadow-writer default is now "loopover", not "gittensory" -- parity-wire.ts:218's own computeParityReadiness call is the one place that still deliberately reaches the preserved gittensory-native DB literal, by explicitly overriding that default, so it's called out separately now rather than folded into the same (now-incorrect) "shared gittensory default" framing.
  • advisory.ts's brand-mention line numbers had drifted (563/895/911/945 -> 580/919/935/969) and the content itself no longer contains any "gittensory" mention at all, only "loopover".
  • cutover-gate.ts:8's own comment-example string is now "JSONbored/loopover,...".
• Left the audit doc's earlier "Findings by file/module" checklist section alone -- it's a deliberately-preserved historical snapshot of what was hardcoded when issue Repo-agnostic capability audit — review/signals stack (Wave 5 prerequisite) #5744's audit was written (describing "gittensory" as a concept, not quoting a literal current value) -- only fixed citations that assert a specific, now-verifiably-wrong fact about current source.

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 -- no issue linked: repo-owner-requested maintainer-equivalent cleanup pass, not a contributor fix tied to a filed issue.

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally (docs-only change; no src/** runtime lines touched, only a .md file under src/review/)
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate (0 vulnerabilities)
• Full npm run test:ci green end to end, exit code captured directly (0)
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries -- N/A, no runtime code changed.

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.
• API/OpenAPI/MCP behavior is updated and tested where needed -- N/A.
• UI changes use live API data or real empty/error/loading states -- N/A.
• Visible UI changes include a UI Evidence section -- N/A, no visible change.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs (none touched here).

Notes

• Fifth in a small series of PRs sweeping the remaining gittensory references left over from the rebrand (docs(selfhost): fix stale gittensory-selfhost self-host doc defaults #6826, chore(config): fix stale gittensory prose in infra/root config files #6841, chore(config): fix stale gittensory prose in wrangler.jsonc comments #6849, docs(miner): fix stale gittensory prose and broken links in loopover-miner docs #6859).

[superagent-security]

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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	a00c984	Commit Preview URL Branch Preview URL	Jul 17 2026, 09:16 AM

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.64%. Comparing base (615dd46) to head (a00c984).
⚠️ Report is 7 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6863   +/-   ##
=======================================
  Coverage   93.64%   93.64%           
=======================================
  Files         685      685           
  Lines       68238    68238           
  Branches    18707    18707           
=======================================
  Hits        63903    63903           
  Misses       3350     3350           
  Partials      985      985           

Flag	Coverage Δ
rees	88.51% <ø> (ø)
shard-1	43.64% <ø> (-0.05%)	⬇️
shard-2	36.81% <ø> (+0.12%)	⬆️
shard-3	32.81% <ø> (+0.09%)	⬆️
shard-4	34.83% <ø> (+0.07%)	⬆️
shard-5	31.85% <ø> (+0.70%)	⬆️
shard-6	45.39% <ø> (-0.31%)	⬇️

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