investigate: is the legacy comment renderer still needed anywhere?

[JSONbored]

Part of #6065. Investigation only -- no code change in this issue.

Problem

Two entirely separate comment-body implementations coexist: the converged renderer (src/review/unified-comment.ts, what every other sub-issue in this epic touches) and a legacy renderer, buildPublicPrIntelligenceComment() (packages/loopover-engine/src/signals/engine.ts:4370, ~5,800-line file), still branded with the <!-- gittensory-pr-panel:v1 --> marker. The switch is in src/queue/processors.ts:9995 -- the legacy path only runs when LOOPOVER_REVIEW_UNIFIED_COMMENT is off OR a repo isn't on the LOOPOVER_REVIEW_REPOS allowlist (src/review/cutover-gate.ts).

None of the redesign work in this epic touches the legacy renderer, meaning any repo still on it won't see any of these improvements, AND review.fields filtering has to be kept in sync in two independently-coded places (unified-comment-bridge.ts:774 and engine.ts:4530) for as long as both exist.

What to check

• Which repos (if any) are currently NOT on LOOPOVER_REVIEW_REPOS / have LOOPOVER_REVIEW_UNIFIED_COMMENT off, i.e. are still actually rendering via the legacy path in production.
• Whether there's a reason it was kept around post-cutover (rollback safety net? specific repo compat issue?) -- check git history / related issues around the convergence cutover.

Outcome

• If confirmed dead (every live repo on the converged path, no rollback dependency): file a SEPARATE maintainer-only/roadmap issue proposing removal of buildPublicPrIntelligenceComment and the legacy code paths that call it. Do not remove it in this issue -- ~5800 lines is a large, separately-scoped change deserving its own PR and explicit go-ahead, not bundled into this epic.
• If still needed: note why here and close as not-planned.

[linear-code]

JSO-4185

[JSONbored]

Investigation findings (static analysis only — no production/VPS access in this session, so this stops short of a definitive answer).

What the code says

• The cloud Cloudflare Worker's committed deployment config (wrangler.jsonc) has LOOPOVER_REVIEW_UNIFIED_COMMENT: "false" and LOOPOVER_REVIEW_REPOS: "" (empty allowlist) as its defaults.
• src/review/cutover-gate.ts's own doc comment: an empty/unset allowlist → every repo processed by that worker falls back to the legacy renderer (buildPublicPrIntelligenceComment), regardless of the global flag.
• wrangler.jsonc:204-207 has an explicit comment on the sibling LOOPOVER_PUBLIC_STATS_REPOS var: "DELIBERATELY separate from LOOPOVER_REVIEW_REPOS above, which went empty when these repos' LIVE processing moved to self-host." — i.e. gittensory/loopover, awesome-claude, and metagraphed's real PR-review traffic no longer flows through the cloud worker's converged path at all; it moved to a self-hosted deployment.
• Self-host .env values aren't committed to this repo (by design — they live on the operator's VPS), so I can't confirm the self-host deployment's LOOPOVER_REVIEW_UNIFIED_COMMENT/LOOPOVER_REVIEW_REPOS values from static analysis. The real PR comment shown at the start of this whole redesign effort (readiness chips, "Copy for AI agents", the 3-col signal table) IS the converged/unified shape, not the legacy one — strong indirect evidence the self-host deployment has it on for at least this repo.

What this means

• On the cloud worker, the legacy renderer is very likely the ONLY reachable path today (converged path is globally dormant there per the empty allowlist) — but per "[[gittensory-deployment-models]]"-type context, there's no hosted multi-tenant product yet, so it's unclear whether the cloud worker is still receiving real GitHub webhook traffic for the PR-review path at all, vs. just serving the public-stats/website endpoints.
• On self-host (the actually-live path for gittensory/loopover/awesome-claude/metagraphed), the converged renderer is almost certainly what's running — but I can't confirm the self-host .env state directly.

Recommendation

Don't remove the legacy renderer (buildPublicPrIntelligenceComment, packages/loopover-engine/src/signals/engine.ts:4370, ~5,800 lines) yet. Before filing a removal PR, the operator should confirm from the actual deployment(s) — not this repo's committed config — whether:

1. The cloud worker still receives any real PR-review webhook traffic (vs. only website/stats endpoints), and
2. The self-host .env has LOOPOVER_REVIEW_UNIFIED_COMMENT=true with every actively-reviewed repo in LOOPOVER_REVIEW_REPOS.

If both check out as expected, removal is a good, well-scoped follow-up — file it as its own issue at that point rather than reopening this one, since it's a large (~5,800-line) deletion deserving its own explicit go-ahead.

Leaving this issue open pending that confirmation rather than closing as not-planned or filing a premature removal PR.

[JSONbored]

Confirmed by the maintainer: the legacy renderer is dead — there's no cloud/hosted deployment running the review pipeline at the moment, so buildPublicPrIntelligenceComment is unreachable in production.

Filing the removal as its own issue (large, ~5,800-line deletion deserving its own scoped PR) and closing this investigation.