Design runs keep their progress through server updates
A /design run no longer starts again at the plan when the server is updated. It hands over between two rounds and continues with the round, scores and versions it already has.
If you use /design, a server update no longer restarts a running design and no longer creates duplicate versions. No action needed.
A /design run works in rounds: it writes a version, builds it, measures it, scores it and then decides whether another round is worth it. Until today a server update interrupted that. The new worker only knew the round number, began again with the plan and created the versions a second time.
Text version
During an update the old worker lets the running model call finish, saves the state of the loop and hands the run over, either at the start of the next round or right before a build. The new worker continues with the same round, the same scores and the same best version. Finished model calls are read back, not bought again.
What changed
The saved state now holds everything the loop needs: the plan, the style direction, the scores so far, the feature log, the best version and the last source.
A run that has just reached its target score ends in the old worker instead of buying another round.
Retry runs on an existing design continue as well. Pressing Stop still wins.
Prices and plans did not change.