3 Commits

Include renames

Author	SHA1	Message	Date
Claude	2df140a3c1	Treat Cloudflare error 1014 as 'channel not published yet' ... A push-triggered first deploy cannot set the first_deploy input, and the domain answers 403/1014 until the Pages project exists. 1014 means nothing exists to preserve, so handle it like a 404. Other 403s still abort. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01JdMNbY5hLR7FjtfEE712xG	2026-10-14 15:53:15 +00:00
Claude	4369d15cec	Add first_deploy dispatch input so the first Cloudflare deploy can bootstrap ... The domain answers 403 (error 1014) until the Pages project exists, which made the carry-over fetch abort the very deploy that would create it. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01JdMNbY5hLR7FjtfEE712xG	2026-10-14 15:39:03 +00:00
Claude	c0fc4fe7d6	Publish dev and prod builds to plg.wallacenet.ca (Cloudflare Pages) ... Both workflows gain a deploy-pages job that stages their channel into one Pages site, carrying the other channel over from the live site. The in-app updater now reads /prod|/dev/latest.json from plg.wallacenet.ca instead of the GitHub API. GitHub releases are still published for one transition deployment so existing installs can fetch the new updater. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01JdMNbY5hLR7FjtfEE712xG	2026-10-14 15:20:47 +00:00