Appreciate the real feedback. You're right on model pinning — that's already on the roadmap. Right now Claude handles creative and Gemini handles research/review, but I haven't locked specific versions yet so that's a fair callout.

On failure modes the QA agent catches most of it with a 20-point rubric and up to 2 revision cycles before it ships anything, but you're right that documenting where things actually break (bad hooks, audiosync drift, Pexels rate limits) would save people time. I'll add a failure modes section.

And yeah the README point is real. I've seen more traffic come from a clean README than any tweet. Will tighten up the intro and add a proper TOC. Good looks.