fix(cloud): enable tag-to-deploy for production cloud worker

The deploy workflow existed but couldn't deploy to production — wrangler:deploy
was hardcoded to --env dev and wrangler.toml had no [env.production] section.
This adds the production env config with a fresh D1 database and parameterizes
the deploy scripts to use CLOUDFLARE_ENV.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jchris

.github/workflows/ci-core-cf-deploy.yaml

@@ -42,6 +42,7 @@ jobs:
           ACCESS_KEY_ID: ${{ vars.ACCESS_KEY_ID }}
           CLOUDFLARE_ACCOUNT_ID: ${{ vars.CLOUDFLARE_ACCOUNT_ID }}
           CLOUDFLARE_DATABASE_ID: ${{ vars.CLOUDFLARE_DATABASE_ID }}
+          CLOUDFLARE_ENV: ${{ vars.CLOUDFLARE_ENV }}
           FP_ENDPOINT: ${{ vars.FP_ENDPOINT }}
           STORAGE_URL: ${{ vars.STORAGE_URL }}
         run: |

cloud/backend/cf-d1/package.json

@@ -10,7 +10,7 @@
     "publish": "echo skip",
     "drizzle:d1-local": "drizzle-kit push --config ./drizzle.cloud.d1-local.config.ts",
     "drizzle:d1-remote": "drizzle-kit push --config ./drizzle.cloud.d1-remote.config.ts",
-    "wrangler:deploy": "wrangler deploy -c ./wrangler.toml --env dev"
+    "wrangler:deploy": "wrangler deploy -c ./wrangler.toml --env ${CLOUDFLARE_ENV:-dev}"
   },
   "keywords": [
     "ledger",

cloud/backend/cf-d1/wrangler.toml

@@ -79,3 +79,20 @@ binding = "FP_BACKEND_D1"
 database_name = "fp-cloud-dev"
 database_id = "b0c1ea22-b733-420c-b812-bea9ffaa1676"
 
+[env.production.vars]
+VERSION = "FP-MSG-1.0"
+
+[[env.production.migrations]]
+tag = "v1"
+new_classes = ["FPRoomDurableObject"]
+
+[env.production.durable_objects]
+bindings = [
+  { name = "FP_WS_ROOM", class_name = "FPRoomDurableObject" }
+]
+
+[[env.production.d1_databases]]
+binding = "FP_BACKEND_D1"
+database_name = "fp-cloud-production"
+database_id = "ee23476b-c3c8-44c9-8388-d9455dd1b00f"
+