fix(deploy): refuse to deploy an assets-only Worker
A deploy on 31 Jul shipped the rose-lawyer Worker with no script. Rose is entirely Worker-rendered, so every page 404'd and the only thing left to serve at the root was the K&S app staged at /firm - the site looked like it had been replaced by Kendry & Slate. wrangler tail named it: 'Cannot tail a Worker which only has assets'. Recovered with wrangler rollback. The cutover script now asserts .open-next/worker.js is non-empty before deploying, and smoke-tests /library for a 200 afterwards.
| Repository | pdombkins/rose_lawyer |
|---|---|
| Author | Peter Dombkins <pdombkins@gmail.com> |
| Authored | |
| Parents | d12ea1ab |
| Stats | 56 files changed , +131 , -73 |
| 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-80ec2f39.md
from inside the repo you want the change in.