[ci] demo-deploy.yml: Cloudflare Pages 'Deploy to z4jdemo' step fails (auth token expired/missing)

[pypv]

Summary

The demo-deploy workflow has been failing on every release tag push since v1.5.1. The 'Deploy to Cloudflare Pages (z4jdemo)' step fails, which prevents demo.z4j.dev from auto-updating after a release.

Symptoms

• Job: 'Build + deploy demo.z4j.dev' conclusion: failure
• Step: 'Deploy to Cloudflare Pages (z4jdemo)' conclusion: failure
• Most recent failure: v1.6.5 (https://github.com/z4jdev/z4j/actions/runs/26492387059)

History

Run trigger	Tag	Date
push	v1.6.5	2026-05-27
push	v1.6.3	2026-05-15
push	v1.6.2	2026-05-14
push	v1.6.0	2026-05-13
push	v1.5.1	2026-05-12

Likely cause

The CLOUDFLARE_API_TOKEN repository secret is expired or missing. Cloudflare API tokens have a default expiry; this one likely lapsed around the time of the v1.5.1 cut.

Suggested fix

1. Generate a new Cloudflare API token at https://dash.cloudflare.com/profile/api-tokens with the 'Edit Cloudflare Pages' template (or custom scope: Account.Pages: Edit)
2. Update the CLOUDFLARE_API_TOKEN secret at https://github.com/z4jdev/z4j/settings/secrets/actions
3. Optionally set a calendar reminder for token rotation before the new expiry

Workaround

Manual deploys via 'pnpm dlx wrangler pages deploy' work fine and are the documented release path per memory rules (sites deploy via wrangler, not git push).

Not a 1.6.5 regression

Pre-existing since v1.5.1.