The cache for dotnet-script execution does not seem to be very compatible with the Windows storage sensor feature.

If the script uses a NuGet package, there is a time stamp gap between the file extracted from the package and the script.dll, so Storage Sense may only delete the package's file.
This may result in an error when trying to run the program because the dependency DLL is not found.

I think this situation can be handled with --no-cache or similar.
However, it may be difficult to notice because the storage sensor works infrequently and the script suddenly stops working.

How about updating the timestamp of the package's extract file when creating the execution cache?