The silent-empty classifier flagged any HTTP-200 turn with decode_tps==0
and t_ms>=1s. But cmd_run zeroes decode_tps when decode_s < 0.1s OR
completion_tokens <= 0 — so a turn that DID produce output but decoded it
in a sub-100ms burst got mislabelled silent-empty. That burst case is
exactly a tool-call turn (small tool_calls payload, empty content) or a
block-diffusion canvas emitted all at once. The DiffusionGemma re-soak
(2026-06-11) false-flagged 4/25 tool-call turns this way.
Switch the discriminator to completion_tokens == 0 (genuine no-output)
when that column is present; fall back to the legacy decode_tps==0 proxy
for pre-2026-05-04 CSVs that lack the column. The summary.md label
already said '0 completion tokens' — now the logic matches it.
Validated: dgemma re-soak turn-log 4->0 silent-empty; synthetic genuine
empty (completion_tokens=0) still flagged; tool-call turn (ct=23,
decode_tps=0) no longer flagged; old column-less CSV still uses the
decode_tps==0 fallback.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
