chore(config): fix stale gittensory prose in infra/root config files

[JSONbored]

Summary

• Continues the repo-wide gittensory -> loopover rebrand cleanup sweep (owner-requested follow-up over the long tail of remaining references). This batch covers root-level and observability config files:
  • .dockerignore was excluding a build-context path named gittensory-config, which no longer exists -- docker-compose.yml mounts the operator's private per-repo config from ./loopover-config today. Fixed the exclusion to match (this one has a small privacy angle: that directory holds runtime-only private review config that must never enter image layers per the file's own comment).
  • .env.example: the documented /gittensory/shot route (real route is /loopover/shot, per src/review/visual/shot.ts), the GittensoryPostgresConnectionPressure alert name (real alert is LoopoverPostgresConnectionPressure, per prometheus/rules/alerts.yml), and the SETUP_OUTPUT_PATH default (src/server.ts falls back to /data/loopover-app.env), plus assorted self-referential prose ("gittensory's central collector" etc.) and illustrative example values (MINIO_BUCKET, DOMAIN).
  • .gitleaks.toml, .loopover-miner.yml.example, orb-manifest.json, vitest.config.ts, loki/loki-config.yml, promtail/promtail-config.yml: same class of stale self-referential prose/title fixes.
  • docker-compose.yml: a stray #gittensory-4327 issue-comment prefix -- confirmed issue GPU passthrough for Ollama + embedding benchmark vs. the current CPU-bound setup #4327 exists in this repo and no other file uses a #<reponame>-NNNN convention, so this was just a leftover repo-name prefix, not a real convention.
  • Renamed test/unit/gittensory-engine-scaffold.test.ts -> test/unit/loopover-engine-scaffold.test.ts (including its describe() title) -- it already asserts the real, current @loopover/engine package identity; only the filename/title were stale. Test files aren't referenced by path elsewhere, so this rename has no other blast radius (verified with a repo-wide grep).
• Deliberately left every dead GITTENSORY_* env var name in .env.example untouched (each is explicitly commented "no longer read" -- the whole point of those lines is to document the old name for anyone migrating a stale deployment) and left the SENTRY_RELEASE/LOOPOVER_VERSION self-host example alone (its gittensory-selfhost@<version> value is intentionally pinned by scripts/deploy-selfhost-prebuilt.sh's actual default and test/unit/selfhost-sentry-release.test.ts) -- added a short inline pointer to why, so this doesn't get "fixed" again by mistake later.

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 (no src/** lines changed; config/docs/test-rename only)
• 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, captured exit code 0 directly (not through a pipe) to be certain
• docker compose config --quiet passes against the edited docker-compose.yml
• 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, no UI code touched.
• Visible UI changes include a UI Evidence section -- N/A, no visible/rendered change.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs (none touched here).

Notes

• Second in a small series of PRs sweeping the remaining gittensory references left over from the rebrand, split by area (small, focused PRs per repo convention). This one covers root/infra config files; docs(selfhost): fix stale gittensory-selfhost self-host doc defaults #6826 covered self-hosting docs. wrangler.jsonc (a handful of similar self-referential comment fixes) is deliberately being handled as its own, even-more-isolated follow-up PR given its stakes as the live Cloudflare Worker config.

[superagent-security]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.63%. Comparing base (8e2f967) to head (6709f9a).
⚠️ Report is 7 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6841   +/-   ##
=======================================
  Coverage   93.63%   93.63%           
=======================================
  Files         683      683           
  Lines       68154    68154           
  Branches    18704    18704           
=======================================
  Hits        63818    63818           
  Misses       3350     3350           
  Partials      986      986           

Flag	Coverage Δ
shard-1	43.66% <ø> (ø)
shard-2	36.83% <ø> (ø)
shard-3	32.67% <ø> (ø)
shard-4	34.80% <ø> (+0.59%)	⬆️
shard-5	31.00% <ø> (-0.57%)	⬇️
shard-6	45.71% <ø> (-0.03%)	⬇️

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