revert: CF migration (operator pivoted back to DO k8s)

[mastermanas805]

Summary

Operator pivoted 2026-05-30: keeping DO k8s for staging, abandoning Cloudflare Containers. Reverts all 3 CF migration PRs: #32 (TF bootstrap + wrangler scaffold + 5 workflows), #33 (TTL=1 + Global Key env vars), #34 (drop cache.tf + nudge).

Removes 2585 lines / 47 files. Specifically:

• terraform/cloudflare/ (13 files): tokens, R2, DNS, Pages, variables, Makefile, README
• wrangler/ (~30 files): 8 service subdirs + top-level README + package.json + node_modules-as-dep
• .github/workflows/terraform*.yml (3 files): plan + per-env apply
• .github/workflows/wrangler-*.yml (2 files): build + deploy

Bug-burner workflow changes + k8s manifests + NR alerts unaffected.

Companion PRs (revert sequence)

• instanodedev/api#??? (revert :staging tag + notify-infra-on-migration.yml)
• instanodedev/worker#??? (revert :staging tag)
• instanodedev/provisioner#??? (revert :staging tag)

What remains for operator cleanup (NOT in this PR)

• CF resources deployed during the session: 8 Workers + Container apps, 1 Pages project (instanode-web-staging), 1 Pages custom domain (staging.instanode.dev), 2 R2 buckets (instanode-tf-state, instant-shared-staging), 6 GH repo secrets (CLOUDFLARE_, CF_ACCOUNT_ID, TF_STATE_R2_)
• 3 GHCR packages made public (instant-{api,worker,provisioner}) — can be reverted to private via per-package settings page
• CF Workers Paid subscription is still active (operator can keep or cancel)

Test plan

• CI: terraform.yml + terraform-apply-*.yml workflows are deleted, so they don't run
• CI: existing validate.yml (k8s manifests) green
• After merge: master has no CF-staging code

🤖 Generated with Claude Code