chore(cloudflare): inventory legacy hosted resources for cleanup

[JSONbored]

Summary

Inventory Cloudflare resources that may remain from the old hosted/cloud Gittensory path and classify what is still used, retained for rollback, or safe to decommission later.

Context

The self-host stack should reduce long-term hosted cost and operational surface area, but resources like D1, R2, KV, Workers, Workers AI, Vectorize, queues, secrets, routes, cron triggers, logs, and dashboards need evidence-based review before anything is removed. D1 databases that cannot be deleted should still be documented so they do not create confusion later.

Requirements

• Review Cloudflare resources without deleting or disabling anything.
• Identify each resource owner, binding, route, trigger, secret dependency, and last-known usage.
• Cross-check repository code, deployment config, dashboards, and any active production routes before declaring a resource unused.
• Separate safe to delete, retain for rollback, unknown, and actively used buckets.
• Document cost and maintainability impact where possible.

Deliverables

• Resource inventory table covering Workers, D1, R2, KV, Workers AI, queues, routes, cron triggers, and related settings.
• Usage evidence for every cleanup recommendation.
• A non-destructive cleanup proposal with explicit approval gates.
• Follow-up deletion issues only for resources with strong evidence.

Acceptance criteria

• No Cloudflare resources are modified by this issue.
• Every cleanup candidate has at least one code/config check and one Cloudflare-side check.
• Ambiguous resources are left in unknown with the exact evidence needed to resolve them.