fix(wrangler): v2 deleted_classes migration — remove SchedulerDO from landing-page worker

[biwasxyz]

What

Adds a v2 Durable Object migration to wrangler.jsonc (all three blocks: top-level, env.production, env.preview) that deletes the SchedulerDO class:

"migrations": [
  { "tag": "v1", "new_sqlite_classes": ["SchedulerDO"] },
  { "tag": "v2", "deleted_classes": ["SchedulerDO"] }
]

Why

During PR #743 experimentation on 2026-05-12, the non-production branch deploy command was temporarily flipped from npx wrangler versions upload to npx wrangler deploy --env preview. Cloudflare Workers Builds overrode the --env preview worker name from landing-page-preview back to landing-page (production), which meant the v1 SchedulerDO migration was applied to the production worker, not the intended preview worker.

Production aibtc.com is currently serving the experimental branch's bundle and has the landing-page_SchedulerDO namespace registered.

Attempted dashboard rollback to a pre-experiment version failed with:

Invalid deployment: The version "5229218f-..." cannot be deployed because it has a resource that was modified: the version depends on Durable Object migration "", but the current deployment is using migration "v1"

This is CF's safety net — rolling back to a version that doesn't know about an applied migration would orphan the DO data.

The fix is a forward migration (v2) that deletes the class, restoring the worker to a clean no-DO state. Once this merges, CI's wrangler deploy applies v2, the SchedulerDO namespace is removed, and aibtc.com runs main's code with no DO baggage.

Test plan

• Local npm run build passes
• After merge, CI's wrangler deploy runs cleanly
• aibtc.com/ returns 200 from main's code (45e70f9 + this commit)
• aibtc.com/leaderboard shows main's pre-PR-feat(leaderboard): /leaderboard page ranked by MCP-submitted trade count + USD volume #743 leaderboard (browser-side Tenero, no SSR volume)
• CF dashboard → Workers → landing-page → Durable Objects: landing-page_SchedulerDO namespace is gone
• No errors in logs.aibtc.com post-deploy

Notes

• Keep both migration entries declared after this lands; removing v1 would break the next deploy with a similar history mismatch.
• The actual SchedulerDO class definition + binding never landed on main, so no source-tree cleanup needed here.
• PR feat(leaderboard): /leaderboard page ranked by MCP-submitted trade count + USD volume #743 remains open; its scheduler work needs to be revisited as a clean follow-up (likely with the class definition inline at the entry point, plus a fresh migration v3 reintroducing it).

🤖 Generated with Claude Code