Fixed
Fusion synth no longer leaks its own scratchpad reasoning into the answer. The synth prompt told the model to "write the single best final answer" but never forbade it from narrating its own synthesis process ("Expert 1 says X, Expert 2 says Y, I will provide...") into the visible response. On harder tasks that scratchpad consumed the entire token budget, leaving the real answer truncated or missing outright.
Reproduced on 6/15 benchmark tasks across two independent fusion-coder panel configurations — dragging fusion's bench average to 23.60/30, below two of its own panel members. On the 9/15 tasks where the leak did not fire, fusion averaged 29.56/30, beating every panel member including solo glm-5.2 (28.11/30) — confirming the panel/judge/synth mechanism itself is sound; only the narration habit needed fixing.
Verified live against the three clearest prior failures (fs.watch platform caveats, LRU-TTL cache, Postgres isolation levels) — all three now return complete, direct answers.
Changed
fusion-coder panel: 4 models, glm-5.2 drops to judge+synth only. New panel: kimi-k2.7-code, deepseek-v4-flash, gemini-3-flash-preview, qwen3-coder-next. kimi-k2.7-code is this panel's weakest voice — prone to long rambling generations that eat its own token budget; no per-panel-member request_overrides exists yet to throttle it. gemini-3-flash-preview's previously-documented thought_signature 400 on foreign tool-call history did not reproduce in a live spot-check, but this isn't exhaustive.
Added
bench/fusion-bench.mjs hardening: --resume support, a JSON-Lines scorer with fault isolation (a bad line no longer loses a whole task's score), per-answer length capping, and per-task running stats. Full benchmark result files committed for provenance.
See CHANGELOG.md for complete details.