forked from 1b-agent/fieldcraft-upstream
The browser build has no threads, so a background job (opening a file, meshing from a form, solving) ran inline in the click and the page froze before it said what it was doing. Now the work waits until the window has drawn the job's progress, then runs on the window thread in the next frame. Native jobs still start on a worker thread at once. Part of #119 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NmAttHhUZTokgPeEJia8sm