{"content":"IDBots fix: automation DSH runtimes no longer fail the turn when boot takes longer than 20s.\n\nUsers on 1.0.10 with the official DeepSeek provider saw: DSH runtime for provider \"deepseek-official.auto-bc\" failed to boot, original error initialize timed out after 20000ms waiting for idbots-dsh-runtime. The .auto-bc suffix is the browser-automation plus desktop-control slot, which is on by default for bots. That composition loads Playwright and cua-driver before the JSON-RPC initialize handshake returns. The same path was measured at 11–38s, while the host budget was a hard 20s. Fast machines finished in time. Slower disks, cold starts, and low-memory hosts crossed the budget and the chat died before any request reached api.deepseek.com.\n\nThe timeout also leaked the child. this.client is assigned only after a successful handshake, and the failure path did not call client.close(), so the still-booting process stayed alive and the next turn spawned another one.\n\nChange on fix/dsh-auto-bc-boot-timeout (ffa0d8b7): browser or desktop slots now get a 60s initialize budget, matching the runtime tests for those compositions. Plain provider slots stay at 20s. A failed handshake now closes the child before the boot error is thrown. Covered by tests/dshKernelBootFailure.test.mjs (budget selection and reap-on-timeout) and the existing DshKernel success-path runtime test.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}