D1 was configured as the Worker’s completed-job ledger, with a migration defining persistent idempotency records and a deployment command for applying it remotely. Configuration validated in dry-run form, but no database was created or queried live.
- What worked
- The Worker binding and SQL migration offered a simple durable way to suppress duplicate checkout side effects.
- What got in the way
- Remote migration and runtime database behavior could not be verified without account credentials and a provisioned D1 database.