docs: record the real cause of the assets-only outages

↗ view on GitHub · Peter Dombkins · 2026-08-02 · ac7c1dd7

Cloudflare Workers Builds was connected to the repo and deploying on every
push with no build command and root directory '/', so opennextjs-cloudflare
build never ran and the Worker shipped with no script. Builds completed in
zero seconds, and deployment history alternated between good manual Wrangler
deploys and broken git ones.

My 31 Jul diagnosis blamed a bare 'wrangler deploy' and the guard I wrote for
the cutover script could never have caught this, because the deploy did not
run locally.

Both integrations are now disconnected: Cloudflare Workers Builds, and the
Supabase GitHub app on the OLD K&S project which had 'deploy to production'
pointed at a database we migrated off.
Repository pdombkins/rose_lawyer
Author Peter Dombkins <pdombkins@gmail.com>
Authored
Parents 7f7588eb
Stats 55 files changed , +97 , -58
Part of Deploy pipeline hardening (Railway backend + Cloudflare Workers frontend)

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-ac7c1dd7.md from inside the repo you want the change in.

⬇ Download capture-commit-ac7c1dd7.md