910633ecb1
The workflow leaves an already-running lean-bench container alone, so a long ingest is never cut off mid-run. That is still the right default, but "left alone" and "up to date" looked identical from outside, and the gap only widens with each build. It cost a full debugging session. The container had been up for six hours on the previous image, so a module added since simply was not in it; the CLI rejected the new flags and every symptom pointed at the new code. The image built from that same commit had the module all along. The container is still not restarted. The build now compares its image id with the one just built and, when they differ, emits a warning and puts a note at the top of the job summary with both ids and the two ways to refresh. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ci5T3gWDhhmqDec3e1XtYZ