chore(cleanup): retire orphaned Cloudflare resources (REVIEW_CONFIG KV, gittensory-review-audit R2, reviewbot-audit R2)

[JSONbored]

Parent: #1826

Problem

The #1826 inventory (see comment) identified 3 Cloudflare resources with zero wrangler.jsonc bindings and zero code references anywhere in the repo:

• REVIEW_CONFIG (KV namespace)
• gittensory-review-audit (R2 bucket)
• reviewbot-audit (R2 bucket — predates gittensory, leftover from the standalone reviewbot project that converged via Convergence: reviewbot → gittensory (native review engine, flag-gated default-OFF) #1036)

wrangler.jsonc itself documents that the API worker "no longer binds Workers AI, Vectorize, R2 review audit storage, or Browser Rendering for review execution" — these are confirmed leftovers from the pre-self-host hosted-review era.

Requirements

• Confirm no self-host or CI tooling reads/writes these resources by any indirect path (e.g. a script, a backup job) before deleting.
• Export/snapshot each resource's contents first as a safety net (even though they're unbound, in case of stale data worth a final look).
• Delete REVIEW_CONFIG, gittensory-review-audit, and reviewbot-audit via wrangler kv namespace delete / wrangler r2 bucket delete (or the Cloudflare dashboard).

Acceptance criteria

• All 3 resources removed from the Cloudflare account.
• No self-host or CI job breaks (nothing referenced them to begin with, so this should be a no-op for running systems).

Ownership

Maintainer-only. No gittensor:* labels — destructive infra cleanup requires explicit owner approval before execution.

[linear-code]

JSO-2511

[JSONbored]

Retired all 3 resources this issue scoped, plus 2 more the original inventory (#1826) missed because it only checked D1/KV/R2/Workers bindings, not Vectorize.

Re-verified from scratch rather than trusting the prior inventory blindly — confirmed zero wrangler.jsonc bindings and zero code references for every resource, traced each one's origin (cloned the archived reviewbot repo to confirm which resources were genuinely its own vs. gittensory's own short-lived convergence-era bindings), and specifically checked that neither the public homepage stats (src/review/public-stats.ts, D1-only) nor the Orb telemetry pipeline (src/orb/*, D1-only, zero KV/R2/Vectorize references anywhere) depend on any of them.

Deleted outright:

• REVIEW_CONFIG (KV) — reviewbot's own namespace (confirmed by matching ID), already empty (0 keys)
• reviewbot-rag (Vectorize) — reviewbot's own RAG index, 356 vectors, regenerable
• gittensory-review-rag (Vectorize) — gittensory's own RAG index, bound 2026-06-05–2026-06-29 during the convergence, deliberately unbound by commit 2572de5 ("Absent ⇒ no RAG"). 2,226 vectors, regenerable from repo_chunks + source repos.

Purge in progress (async — R2 requires emptying before the bucket itself can be deleted):

• reviewbot-audit — 335,312 objects / 4.77 GB. Lifecycle rule (expire-days 0, all prefixes) set; draining on Cloudflare's daily evaluation cycle.
• gittensory-review-audit — 408 objects / 35.5 MB. Same lifecycle rule set. Bound alongside the RAG index above, same removal commit.

Will delete both bucket shells once they report empty.