Cleanup: dormant Cloudflare resources (2026-06 inventory)

[whoabuddy]

Context

This issue tracks the cleanup of dormant Cloudflare resources in the aibtcdev account, identified as part of the May–June 2026 bill-reduction campaign that brought costs from ~$800/mo (April 2026 peak) down to ~$30–60/mo. Phase 4 of quest 2026-06-02-bill-reduction-finalize produced a read-only inventory of dormant workers, KV namespaces, and D1 databases.

No deletions were performed. Every item below requires explicit human confirmation before deletion.

Inventory file: ~/dev/aibtcdev/cloudflare-cleanup-inventory-2026-06.md (written 2026-06-03)

---

High-Confidence Deletion Candidates

The following resources are unbound and/or have had zero traffic for months. Each needs a final human confirm before deletion.

Workers

• aibtcdev-cache — 517 days stale, 0 req/7d, secrets-only bindings
• aibtc-tx-sponsor — 363 days stale, 0 req/7d, no shared resources
• aibtcdev-daos — 77 days stale, 0 req/7d, superseded by production/staging variants
• aibtcdev-daos-preview — 79 days stale, 0 req/7d

D1 Databases

• aibtcdev-d1 — empty (0 tables, 12 KB), unbound, created 2024-12-30
• staging-aibtcdev-d1 — empty (0 tables, 12 KB), unbound, created 2024-12-31

KV Namespaces

• aibtcdev-services — unbound
• production-API_KEYS — unbound (x402 relay uses API_KEYS_preview id 3ce8d9d7)
• production-RELAY_KV — unbound (x402 relay uses RELAY_KV id 5de48f1c)
• staging-aibtcdev-services — unbound
• VERIFIED_AGENTS_preview — unbound preview variant
• worker-logs-LOGS_KV — confirmed orphan (worker-logs workers use worker-logs-staging-LOGS_KV instead)
• x402-api-staging-METRICS — unbound
• x402-api-staging-STORAGE — unbound

---

Needs Investigation Before Decision

• aibtcdev-cache-preview (worker) — binds staging-aibtcdev-cache KV shared with active staging worker
• ordinals-trade-ledger (worker + D1) — dormant but 52 KB of trade history data
• erc8004-indexer-staging (D1) — unbound, 11-table schema, 148 KB
• x402-task-board (D1) — unbound, 4-table schema, 64 KB
• worker-logs-production-LOGS_KV (KV) — unbound, unclear origin
• Several other unbound KV namespaces: METRICS, staging-API_KEYS, staging-INDEXER_KV, staging-RELAY_KV, STORAGE

---

PHASES.md Corrections (candidates that are NOT dormant)

These were listed as candidates in the planning doc but verified active:

• aibtcdev-daos-staging — 554 req/7d (keep)
• aibtcdev-cache-staging — 1,132 req/7d (keep)
• agent-news-design-preview — last deploy 44 days ago (keep, below 60d threshold)
• API_KEYS_preview (KV) — actively bound by both x402-sponsor-relay environments
• staging-aibtcdev-cache (KV) — bound by active aibtcdev-cache-staging

---

Notes

• The full inventory with per-resource binding details, sizes, request counts, and recommendations is at ~/dev/aibtcdev/cloudflare-cleanup-inventory-2026-06.md
• KV ops-per-period are not exposed via standard CF REST/GraphQL APIs; binding presence was used as the dormancy proxy
• D1 read_queries_24h from wrangler d1 info was used for activity; 24h window only
• Worker request counts are from CF GraphQL workersInvocationsAdaptive (7-day window ending 2026-06-03)