The Scorer Was Silently Dropping Half Its Shot Scores

What we shipped on 2026-07-09 Two alerts fired on the same post -- hero_render_fallback on shots 4 and 8, vision_scorer_unavailable on 5 of 12 shots -- and pulling that thread unraveled into three separate defects in one sitting (PR #2224). shot_vision_qa.score_shot_frame() was calling the vision model with max_tokens=300 and no think= flag. qwen3-vl burns part of that budget on a <think> trace before it ever gets to the JSON answer -- the same failure mode multi_model_qa._check_image_relevance hit and fixed months ago by raising num_predict from 400 to 1024 (poindexter#563). 300 tokens was smaller than an already-proven-insufficient number. This scorer had been quietly dropping something like 42% of shot scores, which lines up almost exactly with the ~45% figure flagged in the video-quality audit back on 2026-07-02. Chronic, not new -- and nothing had touched this file since. While we were in there, wan2_1.py's /generate call turned out to be hardcoding timeout=300 on the indi