When Your Content Bot Hits an LLM Quota, Ship the Fallback

A publishing bot that depends on one LLM provider has a boring failure mode: the workflow is green, but nothing gets published. I hit that during cycle. The de.to key was present, the command was read, and the article module simply returned no action after generation failed with llm_json. That is the kind of failure that looks harmless in CI and expensive in a content pipeline. The fix is not optimism. The fix is a fallback path that produces a plain, useful, bounded article without calling another model.