* claim: #2929 Co-Authored-By: Claude Code <noreply@anthropic.com> * OK off the window thread: a job that has just started waits a frame (#2929) The off-thread evaluation of a feature dialog was taken up in the same frame it started, so a job whose worker had already finished was applied at once and the dialog never said it is computing. Under load the window thread is held up between starting the job and the check, and the feature appears where the computing state belongs - which is what made `apply_off_thread_tests::cancel_while_computing_applies_nothing` fail with `assertion failed: h.app.applying.is_some()`. A job that has just started now waits one frame: its result is taken up from the next one, so the dialog says it is computing before the feature appears. The app waits APPLY_AT_ONCE (150 ms) for the evaluation before it lets the window go on, so a job only exists when the evaluation took longer than that: the change shows the computing state for a frame in the 150-151 ms window, and nothing else moves. Co-Authored-By: Claude Code <noreply@anthropic.com> --------- Co-authored-by: jeremymiribung-blip <jeremymiribung-blip@users.noreply.github.com> Co-authored-by: Claude Code <noreply@anthropic.com>