deploy-cloudflarelisted

# Deploy Cloudflare Runs the one-time setup a Cloudflare Pages deploy needs before the seeded `deploy.yml` workflow can run, stopping twice for the two acts only the operator can take. ## Guards - If `wrangler whoami` fails, stop: `❌ wrangler is not authenticated. Run wrangler login, then re-invoke.` - If `gh auth status` fails, stop: `❌ gh is not authenticated. Run gh auth login, then re-invoke.` - Never accept a Cloudflare API token as input, in a prompt, an argument, or a file. Verify a secret's presence with `gh secret list` rather than asking for or reading its content. - Never reimplement `wrangler pages project create` or `gh secret set` as a hand-built HTTP call. Call the tools directly. - If the project name is not supplied, derive it from the repository's own name (`basename` of `git remote get-url origin`, stripped of a trailing `.git`) and confirm it in the preview rather than asking first. ## Step 1: create the Pages project ```bash wrangler pages project create <project-name> ``` Report the command's own failure output and stop rather than retrying on a name collision. A project already existing under that name is the operator's to resolve. ## Step 2: fetch and set the account ID Fetch the account ID from `wrangler`'s own authenticated session rather than asking the operator to copy it from the dashboard. The dashboard displays the account ID truncated, and a value copied from there fails the deploy silently: ```bash wrangler whoami ``` Parse the accou