Distillation

<observations> Date: Jul 21, 2026

🟡 (09:09) [tool:result] Cloudflare docs "Pages" page (wrangler command reference) confirms wrangler pages dev [DIRECTORY] [COMMAND] flags: --compatibility-date, --compatibility-flags (alias --compatibility-flag), --ip, --port, --inspector-port, --binding/--b, --r2, --live-reload (default: false), --persist-to.
🟡 (09:09) [tool:result] Docs confirm wrangler pages project delete [PROJECT-NAME] flags include --production-branch, --compatibility-flags/--compatibility-flag, --compatibility-date.
🟡 (09:09) [tool:result] Docs confirm global/common flags across pages subcommands: --v/--version, --cwd, --config/-c, --env/-e, --env-file, --experimental-provision (aliases --x-provision, default: true), --experimental-auto-create (alias --x-auto-create, default: true), --install-skills (default: false), --profile.
🟡 (09:09) [tool:result] wrangler pages secret subcommands accept [FILE] (JSON key-value pairs or .dev.vars KEY=VALUE format) and --project-name/--project flag.
🟡 (09:09) [tool:result] Cloudflare docs "Branch deployment controls" page: example API call to set production branch is curl --request PATCH "https://api.cloudflare.com/client/v4/accounts/{account_id}/pages/projects/{project_name}" with header Authorization: Bearer <API_TOKEN>, body {"production_branch": "main"}".
🟡 (09:09) [tool:result] Branch deployment controls doc: rule evaluation order is (1) Excludes, (2) Includes, (3) Skip — excludes processed first, then includes; branches matching neither are skipped. Supports static branch names (e.g., staging, dev) and wildcard syntax at start or end of a rule. Example use case: excluding Dependabot-created branches from triggering deployments.
🟡 (09:09) Assistant concluded (Q1 default production branch, per official docs): Cloudflare Pages defaults the production environment to "the branch you first push" — there is no universal hardcoded default of main or production. For Direct Upload projects

Distillation

Observations