D1 migrations deployment

[kentcdodds]

Add Cloudflare D1 migration application to the CI deploy workflow and update wrangler-env.ts to use the local wrangler binary to prevent "no such table" and "wrangler not found" errors in production.

This change ensures D1 migrations are applied during deployment to prevent schema-related errors and addresses CI failures where the wrangler CLI was not globally available. Documentation for the CLOUDFLARE_API_TOKEN has also been updated to reflect the necessary D1 edit permissions.

---

 

---

Note

Medium Risk
Changes the production deploy pipeline to run remote D1 migrations, which can fail or apply incorrect schema if misconfigured. Behavior is limited to main deploys but affects live infrastructure.

Overview
Ensures production deployments apply Cloudflare D1 schema changes by adding a d1 migrations apply ... --remote step to the main deploy job before Workers deployment.

Updates wrangler-env.ts to prefer the project-local node_modules/.bin/wrangler (with fallback to Bun.which) to avoid CI failures when wrangler isn’t globally available. Docs now clarify that CLOUDFLARE_API_TOKEN needs D1 edit permissions in addition to Workers deploy access.

^{Written by Cursor Bugbot for commit 13491f0. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}