fix(review): restore engine-parity after gittensory rename drift

[JSONbored]

Summary

• Urgent fix: PR docs(review): rename gittensory prose to loopover in src/review (batch A) #5883 (part of rebrand epic Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705) renamed brand-name prose in src/review/guardrail-config.ts and src/review/linked-issue-label-propagation.ts but not their byte-identical twins under packages/loopover-engine/src/review/**, which scripts/check-engine-parity.ts requires to stay in sync. This broke the parity check on main (verified by cloning a fresh main and running the script directly — 2 real failures).
• Aligns the two engine-side files' comment text with the host copies. No logic changes.
• Also fixes test/unit/finding-taxonomy.test.ts, which had a stale hardcoded assertion still expecting the pre-rename "gittensory://finding-taxonomy" MCP resource URI literal — the constant itself (FINDING_TAXONOMY_URI) was already correctly renamed by docs(review): rename gittensory prose to loopover in src/review (batch A) #5883; only this one test's pinned expectation had drifted. Every other consumer of this constant imports the symbol, so nothing else was affected.

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 — N/A, maintainer-authored hotfix restoring a check broken by an earlier same-day rebrand-cleanup PR (Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705/docs(review): rename gittensory prose to loopover in src/review (batch A) #5883), no linked-issue gate applies to owner PRs.

Validation

• git diff --check
• npx tsx scripts/check-engine-parity.ts — confirms ok (was failing on main before this fix)
• npm run test:coverage — full unsharded run, 100% green
• Full npm run test:ci gate run locally, exit 0

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

Notes

• This is a priority fix for a break on main, not part of the normal batched-PR sequence for epic Epic: complete the gittensory -> loopover rebrand (full cutover, no dual-support) #5705.

[superagent-security]

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