Add Cloudflare Pages as a publishing destination

[livid]

Summary

Add Cloudflare Pages Direct Upload as an optional publishing destination, similar to the existing SSH rsync support.

User Input (minimal — 3 values)

1. Account ID — from Cloudflare dashboard URL
2. API Token — with Cloudflare Pages:Edit permission
3. Project Name — the Cloudflare Pages project name

Model Changes (MyPlanetModel.swift)

Add 4 properties:

@Published var cloudflareEnabled: Bool? = false
@Published var cloudflareAccountID: String?
@Published var cloudflareAPIToken: String?
@Published var cloudflareProjectName: String?

Boilerplate touchpoints in MyPlanetModel.swift:

• Add 4 properties
• CodingKeys enum — add 4 cases
• init(from decoder:) — 4 decodeIfPresent calls
• encode(to:) — 4 encodeIfPresent calls
• hash(into:) — 4 hasher.combine calls
• == operator — 4 comparisons
• importBackup — restore the 4 properties from backup

Publish Flow

In publish(), add a Cloudflare Pages path similar to the SSH rsync pattern:

• Check cloudflareEnabled flag
• Validate account ID, API token, and project name are present
• Use Cloudflare Pages Direct Upload API: POST /accounts/{account_id}/pages/projects/{project_name}/deployments with files from publicBasePath as multipart upload
• Auto-create the Pages project if it doesn't exist

UI Changes

• Add a "Cloudflare Pages" section in the Publishing settings tab (alongside the existing SSH rsync and IPNS toggles)
• Toggle + 3 text fields (Account ID, API Token, Project Name)

Notes

• The Direct Upload API accepts files as multipart form data — no need for Wrangler CLI
• Pattern follows existing integrations (Filebase, SSH rsync, etc.)

[livid]

Implemented in 9683345.

Current progress:

• added Cloudflare Pages as a publish destination using the Direct Upload API
• fixed the asset upload and manifest flow so Pages serves the deployed site correctly, including content-type metadata and 32-character asset hashes
• publish timer now only refreshes IPNS; Cloudflare Pages publishes only run on real publish actions
• UI now shows the stored Pages URL in the sidebar Open menu and in the planet edit view after a successful deploy from this build
• consolidated SSH rsync and Cloudflare Pages logs into the shared publish log view

Notes:

• the Pages URL is resolved from the successful deployment response; the app does not synthesize a production hostname from the configured project name
• existing Pages-enabled planets need one successful deploy from this build before the new Open pages.dev action appears

Built successfully with Xcode 16.4 targeting macOS 12.