Distillation

["6f8a8f4246765f75d2ec00bc35d805d7","27f61f8d1e8b7467f37ecd1e43e16ba5","39cbba714390fdbdbc6f34e05ccc7ab8"]

<observations> Date: Jul 21, 2026 * 🔴 (10:19) Docs updated in docs/src/content/docs/targets/cloudflare.md: `deployType` default flipped to `worker` (was `pages`); note added stating Cloudflare is steering new projects to Workers (optionally with static assets) and positioning Pages as legacy — Pages remains supported via `deployType: pages`. * 🔴 (10:19) Docs state `productionBranch` is now optional; when omitted, Craft reads it from the Cloudflare API so the release "lands on production." Only used for `deployType: pages`. * 🔴 (10:19) Docs state `CLOUDFLARE_API_TOKEN` is Required=Yes (permission to deploy Pages/Workers), passed to `wrangler` via the environment, "never on the command line." `CLOUDFLARE_ACCOUNT_ID` is Required=No — described as "an identifier, not a secret"; when unset, `wrangler` auto-discovers it for single-account tokens. * 🔴 (10:19) Docs added a note: Cloudflare deployments authenticate via API token only — no OIDC/keyless option in `wrangler`; `CLOUDFLARE_API_TOKEN` must be provided as a CI secret. * 🔴 (10:19) Docs added "Production deployments (Pages)" section: `wrangler pages deploy --branch <X>` deploys to production only when `<X>` exactly matches the project's server-side production branch; any other value silently produces a *preview* deployment (not an error). Resolution order: (1) if `productionBranch` set in config, used verbatim; (2) else if account ID known, Craft calls Cloudflare API `GET /accounts/{id}/pages/projects/{name}` (same call wrangler makes internally, no extra token