Steps to Make Accept: text/markdown Work Everywhere
I thought I had built Accept-header Markdown for AppHeat. Production had other plans, because Cloudflare was skipping the Worker entirely.
Use this path for Cloudflare app decisions, database constraints, runtime tradeoffs, and the places where simple choices have to survive real users.
Choose boring primitives until usage proves the need for a heavier system.
Treat deployment, secret handling, and observability as part of the product.
Keep local experiments tied to production constraints.
I thought I had built Accept-header Markdown for AppHeat. Production had other plans, because Cloudflare was skipping the Worker entirely.