fix: default NODE_ENV to "development" and override in production env

[mahata]

Summary

• Changes the top-level [vars] in wrangler.toml to default NODE_ENV to "development" (used by wrangler dev during local development).
• Adds an [env.production.vars] block that overrides NODE_ENV to "production" for wrangler deploy --env production.
• Removes the now-redundant --var NODE_ENV:development flag from the Playwright webServer command in playwright.config.ts.

[Copilot]

Pull request overview

Adjusts Cloudflare Workers environment variable defaults so local development (wrangler dev) runs with development semantics by default, while production deployments can explicitly override to production behavior.

Changes:

• Default NODE_ENV to "development" in wrangler.toml [vars].
• Add [env.production.vars] to override NODE_ENV to "production".
• Remove the Playwright webServer wrangler dev --var NODE_ENV:development flag, relying on wrangler.toml defaults.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
wrangler.toml	Sets default NODE_ENV to development and adds a production override block.
playwright.config.ts	Simplifies wrangler dev invocation by removing the explicit NODE_ENV var flag.

[Copilot]

Setting the top-level [vars] NODE_ENV to "development" makes the default Wrangler environment (used by wrangler deploy with no --env) run with development settings. Since the repo’s deploy flow is pnpm deploy → wrangler deploy (no --env production), this change can unintentionally deploy a production worker with NODE_ENV=development (e.g., session cookies not marked secure, dev/test-only endpoints enabled). Consider keeping the default environment as production-safe and using a dedicated dev/e2e env (or .dev.vars) to set NODE_ENV=development, or ensure all deploy commands/docs use --env production.

Suggested change

	NODE_ENV = "development"
	NODE_ENV = "production"