Establish blue/green deployment flow for mojidata-api D1

[mandel59]

Summary

Current D1 deployment flow imports generated SQL dumps directly into the D1 databases bound by the live Worker. That is not safe for no-downtime deployment because the Worker can read a partially dropped, partially imported, or schema-incompatible database during import.

Goal

Change the D1 operational flow so database refreshes are treated as immutable blue/green releases:

1. create new D1 databases with a release label
2. import mojidata and idsfind data into those new databases
3. smoke-test the new databases through a non-production Worker target
4. promote by switching Worker bindings to the new database IDs and deploying the Worker
5. keep the previous database IDs available for rollback

Acceptance criteria

• Production docs no longer recommend importing directly into the currently bound D1 databases.
• Repository scripts can create/import a release pair of D1 databases without mutating the active Worker bindings.
• Promotion is an explicit step that updates Worker bindings only after import and smoke validation.
• The flow records enough metadata to identify the promoted and previous database IDs.
• Rollback is documented as switching bindings back to the previous database IDs and redeploying.

Related

• Related: Add Unihan reverse lookup table to reduce D1 rows read #35

[mandel59]

Post-deploy cleanup follow-up (2026-05-03 JST)

The 20260503-bg blue/green release is live on the existing top-level Worker.

• Worker: https://mojidata-api-d1.mandel59.workers.dev
• Worker version: 8b4a5fd9-6c22-4f8b-a448-4e91c02d9b02
• cloudflare bookmark: 0ac5aecc Promote D1 blue-green release
• Active release DBs:
  • MOJIDATA_DB: mojidata-api-d1-mojidata-20260503-bg (7d7a62e6-bc66-4c83-8716-ceab92fb972d)
  • IDSFIND_DB: mojidata-api-d1-idsfind-20260503-bg (950b99cd-dc7f-451f-b7fe-2f01385fb3df)
• Previous rollback DBs retained:
  • MOJIDATA_DB: mojidata-api-d1-mojidata (7db8cd1a-c166-4192-a90e-0c1e782a1654)
  • IDSFIND_DB: mojidata-api-d1-idsfind (095f48e1-4a92-481f-83c8-ef71a35ac98f)

Cleanup work to track:

• After the observation/benchmark window, decide whether rollback is still needed. If not, delete the previous inactive D1 pair to stay under the D1 database-count limit.
• Before deleting old DBs, verify wrangler.jsonc, the active Worker deployment, and the cloudflare bookmark still point at the 20260503-bg DB IDs.
• Make rollback metadata durable. The deploy run wrote /tmp/mojidata-api-d1-rollback-20260503-bg.json, but /tmp is ephemeral; either store the manifest in an ops artifact location or document how to recreate it from the DB IDs above.
• Decide whether the top-level Worker remains the production target. env.production currently has placeholder D1 IDs and no Cloudflare Worker exists for mojidata-api-d1-production; either provision it intentionally or remove/clarify the placeholder environment.
• Improve promote-release so it preserves JSONC comments or rewrites only the d1_databases block. The current script rewrites the config as JSON, which can create unrelated comment churn.
• Add a post-deploy verification command that runs smoke tests, checks Cache-Control: no-store, and measures the D1 rows-read budget for unihan_fts (for example 漢 should stay around indexed lookup scale, not full-table scan scale).

[mandel59]

棚卸しメモ (2026-05-05): open 維持。D1 Free plan 検証と直近の blue/green deploy は完了済みだが、この issue は production 運用フローの残作業を追跡する場として残す。次は inactive D1 pair の cleanup 判断、rollback manifest の永続化、production env placeholder の整理、promote-release の JSONC 差分最小化、post-deploy verification command の整備。