Restore Cloudflare Pages permission for the manual GitHub release

[sarthakagrawal927]

Blocker\n\nManual workflow run 31301330294 reached Cloudflare but failed with API authentication error 10000 when reading the chess-9a0 Pages project. The same exact main SHA was successfully released from the already-authenticated local Fleet session, so the product is live and current; only the GitHub secret's authorization is blocked.\n\n## Owner action\n\nUpdate or replace the repository's CF_API_TOKEN GitHub secret with a token scoped to account 7d048325699a5acddb44d3be31cf6ba9 and Cloudflare Pages Edit, without exposing its value. Then rerun the manual Deploy to Cloudflare Pages workflow.\n\n## Acceptance\n\n- The workflow deploys origin/main successfully.\n- Production smoke passes.\n- The secret value is never printed or committed.

[sarthakagrawal927]

Chess main 0a7d413 is live on Pages and the production smoke plus COEP/COOP headers pass. PR #24 removed the obsolete workflow/runtime warnings and merged green. This issue now tracks only the GitHub-held CF_API_TOKEN permission: update or replace it with Pages Edit for the configured account, then rerun the manual workflow. No secret value was read or changed.

[sarthakagrawal927]

Resolved. Replaced the Cloudflare Pages API token, updated the CF_API_TOKEN GitHub Actions secret, and completed a production deployment with smoke verification. I also removed the Node.js 20 deprecation warnings by updating checkout to v7 and pnpm/action-setup to v6 across the workflows. CI, docs, and deploy all pass on commit 6906c1d with zero check annotations. Deploy evidence: https://github.com/Significant-Hobbies/chess/actions/runs/31309400371