GitHub Pages deploys on push via .github/workflows/deploy-github-pages.yml; the Cloudflare stack still requires a manual npm run deploy (wrangler) and npm run sync for R2 media. Add a workflow so pushing to main builds, syncs media, and deploys — the fork (catalogue-artifact) is the first consumer.
Also found during #1: the README's Cloudflare section already promises this automation — "A GitHub Action uploads them to R2, writes the URLs into your entry file, and removes the originals from the repo", a 5-secret table, and "every push rebuilds and republishes". None of it exists; scripts/sync-media.js lives only in the fork. Fixing this issue means upstreaming the sync script, adding the workflow, and reconciling that README section with what actually ships.
Migrated from Linear A-89 · created 2026-07-25 · Backlog · Priority: Medium
GitHub Pages deploys on push via
.github/workflows/deploy-github-pages.yml; the Cloudflare stack still requires a manualnpm run deploy(wrangler) andnpm run syncfor R2 media. Add a workflow so pushing to main builds, syncs media, and deploys — the fork (catalogue-artifact) is the first consumer.Also found during #1: the README's Cloudflare section already promises this automation — "A GitHub Action uploads them to R2, writes the URLs into your entry file, and removes the originals from the repo", a 5-secret table, and "every push rebuilds and republishes". None of it exists;
scripts/sync-media.jslives only in the fork. Fixing this issue means upstreaming the sync script, adding the workflow, and reconciling that README section with what actually ships.Migrated from Linear A-89 · created 2026-07-25 · Backlog · Priority: Medium