The first run of this scenario reported "no podcast_episodes row — the render sweep never reached this mission" while the pipeline was working. It was not: the render is a sweep every two minutes followed by a text-to-speech call that takes minutes on a full dialogue, and the assertion fired the instant the mission completed. That asserts the worker is FAST, not that it works. It now waits up to CR_EPISODE_TIMEOUT (default 900s) for a verdict and reports how long it waited when none arrives, so a timeout reads as a timeout rather than as a product defect. Everything else in that run passed, including the one this scenario was written for: analysis.md is on main (6717 bytes), where the same path returned 404 before the merge fix. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01WZb5A2kfVfjpdwSochkuHz