chore(migration): inventory hosted resources before self-host cleanup

[JSONbored]

Parent: #1819

Context

The review system has moved toward a self-hosted/local execution model, but Cloudflare-era and hosted resources may still exist for API, Orb ingress, historical data, rollback, public stats, or migration support.

This issue is inventory and migration planning only. It must not delete or disable any hosted resource without explicit follow-up approval.

Requirements

• Inventory active and legacy Cloudflare Workers, D1 databases, KV namespaces, R2 buckets, queues, secrets, routes, cron triggers, and dashboards relevant to review operation.
• Classify each resource as keep, migrate, retire later, or unknown.
• Identify which resources still feed public stats, Orb ingress, historical review data, migration export, or rollback safety.
• Define data export/import requirements for historical review data, repository settings, audit rows, and other non-secret operational state.
• Ensure export boundaries redact or drop cloud-scoped secrets, encrypted token envelopes, session hashes, webhook dedup material, and any private config values.
• Produce a decommission checklist that is blocked until migration verification passes.

Deliverables

• Hosted resource inventory with owner, purpose, current usage, data sensitivity, and recommended action.
• Migration plan with row counts/checksums where data moves into self-host storage.
• Redaction checklist for export/import scripts and generated artifacts.
• Explicit rollback plan for resources kept temporarily.
• Follow-up issue list for any destructive cleanup, each requiring separate approval.

Acceptance criteria

• No hosted resource is removed by this issue.
• Maintainers can see exactly what still depends on hosted/cloud infrastructure.
• Historical data migration has a verification strategy before cloud stores are considered retireable.
• Secret-bearing or cloud-scoped material is never exported into public artifacts or self-host docs.

Validation

• Run read-only inventory commands or API queries.
• Run export redaction tests where applicable.
• Compare source/target row counts and checksums for any migration dry-run.

Ownership

Maintainer-only. No gittensor:* labels.

[JSONbored]

Cloudflare resource inventory (2026-07-02)

Read-only inventory, no resources touched. Cross-checked every Cloudflare D1/KV/R2/Workers resource on the account against wrangler.jsonc bindings and a full grep -r across src/ for code references.

gittensory-owned resources

Resource	Type	Bound in wrangler.jsonc?	Code references?	Classification
gittensory (D1, b2c79dd6-7771-4b1f-aa6b-085d5f3e9528)	D1	Yes (DB)	Yes, extensively	Keep — the live production DB
gittensory-api	Worker	n/a (this is the worker)	n/a	Keep — active, auto-deploys on merge to main
gittensory-ui	Worker	n/a	n/a	Keep — active
gittensory-jobs / gittensory-jobs-dlq	Queues	Yes (producer + 2 consumers)	Yes	Keep — broker/API maintenance lane
RateLimiter	Durable Object	Yes	Yes	Keep
cron */2 * * * *	Trigger	Yes	Yes (broker/API maintenance tick, comment confirms "Cloudflare does not execute hosted reviews")	Keep
REVIEW_CONFIG	KV namespace	No — zero kv_namespaces entries anywhere in wrangler.jsonc	No — zero matches repo-wide	Retire candidate
gittensory-review-audit	R2 bucket	No — zero r2_buckets entries in wrangler.jsonc	No — zero matches	Retire candidate — wrangler.jsonc itself documents why: "The Cloudflare API worker no longer binds Workers AI, Vectorize, R2 review audit storage, or Browser Rendering for review execution."
reviewbot-audit	R2 bucket	No	No	Retire candidate — predates gittensory itself; leftover from the standalone reviewbot project that converged into gittensory (#1036), never gittensory's own resource

wrangler.jsonc's own vars-block comments corroborate this independently of the grep: "Hosted reviews are retired. Cloudflare now serves the public API + Orb broker only; review execution runs in the self-host container... The Cloudflare API worker no longer binds Workers AI, Vectorize, R2 review audit storage, or Browser Rendering for review execution."

Not gittensory's (excluded from this inventory)

metagraphed-health, transmogrifi/transmogrifi-dev (D1); metagraphed, metagraphed-ui, metagraphed-data-api, transmogrifi-*, heyclaude-*, aethereal-*, finance-portability-web, cloudflare-remote-mcp-server-authless (Workers); METAGRAPH_CONTROL, heyclaude-mcp-cache-prod (KV); claudepro-static-content, metagraphed-artifacts, metagraphed-backups, heyclaude-submission-gate-audit, homelab-screenshots, transmogrifi-* (R2) — all belong to other products on the same Cloudflare account.

Recommendation

No resource was removed by this comment (per this issue's own constraint). Filing a separate, narrowly-scoped follow-up issue for the actual retirement of the 3 orphaned resources above (REVIEW_CONFIG, gittensory-review-audit, reviewbot-audit) so that destructive step gets its own explicit approval, per this issue's acceptance criteria.

[JSONbored]

Follow-up: the retire-candidates identified in the inventory above are now retired — see #2644 (also caught 2 more orphaned Vectorize indexes the original inventory didn't check for). Leaving this issue open since its broader scope — historical review-data export/import verification — is separate and untouched by that cleanup.