If eval_every is positive but max_iterations falls before the next scheduled eval iteration (including resume cases where current_iteration is already past the last eval boundary), log a one-time warning at run start so the user notices the misconfiguration. We deliberately do not force an end-of-run eval, which would distort time budgets and reproducibility. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>