maddy-score-tunerlisted

# maddy-score-tuner ## QC Spec compliance — assert before every tuning edit Any difficulty/variance lever you pull must STILL satisfy the QC Spec (`.claude/QC-SPEC.md`). Before recommending a change, assert it does not breach: - **No Binary Bundling** — never recover variance by AND-ing more heterogeneous checks into one subscore. - **Incremental Rewards / No Dead Weights** — no subscore left always-0 or always-1; every lever keeps both subscores varying. - **Functional Subscore Variance** — at least one functional subscore takes ≥2 distinct values across a batch. - **Equal Weights** — never rebalance weights to hit a number. - **Functional Tests as Subscores / No Answer Leakage** — don't convert a functional subscore into static matching, and don't leak the answer to manufacture passes. A lever that lowers avg by breaching any of these is NOT a valid fix — pick a different lever. ## Execution Mode — FULLY AUTONOMOUS **NEVER call `ask_user` or pause for confirmation.** Pick the best path and execute it immediately. ## Goal Tune task difficulty and variance safely. **The objective is not to "pass" — it is to keep avg rollout score < <TARGET_MEAN> with both subscores varying, neither deadweight, and the two subscores decorrelated.** Every edit must be the smallest reversible change that explains the observed symptom. Invoked when: - Rollouts regress (avg ≥ 0.60) - A subscore becomes deadweight (always 0 or always 1) - The two subscores move together every batch (correla