Temporary Cloudflare deployment

Prepare a Worker and make the proposed deployment reviewable before the public exposure step. Confirm authorization for the first public deployment unless the user already explicitly authorized that action. Authorization persists for the agreed scope; do not deploy as a side effect of ordinary editing or QA.

Requirements and boundaries

• This workflow uses pinned wrangler@4.102.0, Node 22+, npm, and Python 3. The release supports temporary previews. Verify package/runtime compatibility before setup.
• A temporary deployment is public. Explain the claim/expiry information returned by Wrangler; do not promise production availability or permanent hosting.
• Do not remove existing Cloudflare credentials or log out to force this flow. If the user is authenticated, explain the conflict and resolve their intent.
• Respect the service's terms. Claim URLs grant ownership: keep them private.

Workflow