Rejected Alchemy IaC framework for craft's Cloudflare target

Considered adopting Alchemy (alchemy.run/cloudflare, TS IaC framework, Terraform/Pulumi alternative for Cloudflare) for craft's Cloudflare target — rejected. Reasons: (1) state ownership mismatch — Alchemy is stateful IaC expecting to own the whole resource stack (Workers/D1/KV/R2/DNS), but craft targets are stateless publish steps shipping a prebuilt *-cloudflare.zip artifact; (2) reverses craft's deliberate 'no new runtime dependency' choice to shell out to Wrangler [[019f664e-b8f0-7322-b858-e243a203b289]] — Alchemy is heavier and bun-first while craft runs on Node; (3) Alchemy's Workers-first/Pages-de-emphasized stance adds nothing Wrangler doesn't already give craft; (4) wrong layer — Alchemy belongs upstream, in a user's own build step, not inside craft's publish target. Only relevant if a downstream project (e.g. getsentry/toolkit docs site) wants IaC to manage its own CF resources — orthogonal to craft, which still just deploys built output either way.