Desktop scoped-store cleanup can race later writes on Windows #45154

Description

In a Windows desktop development build, deleting or clearing scoped state also starts asynchronous cleanup of the empty store file. A later write can overlap that cleanup, producing repeated EPERM errors in the main process and making composer interactions feel sluggish.

Plugins

None

OpenCode version

1.18.22 (source checkout)

Steps to reproduce

1. Run the Windows desktop development build.
2. Use session or composer flows that delete or clear scoped state while a later interaction writes to the same store.
3. Observe intermittent store-file EPERM errors and reduced responsiveness.

Screenshot and/or share link

Not attached; reproduced locally in the native Windows app.

Operating System

Windows 11 Home

Terminal

PowerShell