fix(windows): retry owned runtime cleanup on sharing conflicts

Bound retries of native close conflicts at the retained runtime owner. Preserve exact failures and later retry authority after exhaustion. Attempt all verifier cleanup while retaining primary failures; extend held-file Windows verification.

Refs #4136, #4185

Co-authored-by: DeryFerd <deryferdikao125@gmail.com>

native/windows/README.md

@@ -111,9 +111,14 @@ automatically. Alternatively, build it using the Linux/MinGW lane above.
 - Cleanup walks locked directory objects, removes files by handle, and unlinks
   reparse entries without traversing their targets. Failed removal retains the
   root and ancestor leases for retry; a partially removed runtime accepts only
-  cleanup, and its registry entry remains until removal succeeds. The owned root
-  handle includes attribute-write access so cleanup can clear a read-only marker,
-  matching the child cleanup handles. Normal close, cancellation,
+  cleanup, and its registry entry remains until removal succeeds. The runtime
+  owner retries only native close failures with Win32 sharing/lock codes 32/33,
+  for at most ten attempts with a 100 ms delay between attempts. Other native
+  errors are returned immediately; exhausting the retry budget preserves the
+  runtime owner for a later explicit close. These cleanup retries do not use an
+  analysis cancellation signal and schedule up to 900 ms of backoff, in
+  addition to native cleanup time. The owned root handle includes attribute-write access so cleanup can clear a
+  read-only marker, matching the child cleanup handles. Normal close, cancellation,
   startup failure, and timeout release provider resources. Abrupt owner death
   kills the owned job. The Android provider additionally uses a detached helper
   that owns its private runtime directory and cleans it when the owner pipe
@@ -133,7 +138,9 @@ text do not establish a safe retry. Analysis errors propagate the producer's
 retry disposition through JavaScript, source-map and WABT workflows; transient
 failures report `category: unavailable` and retain the original reason.
 Incomplete cleanup blocks an operation retry until its owned resources settle.
-REA adds no automatic retry loop or new analysis cache for this behavior.
+The close-stage retry is separate from allocation and analysis retries: it
+repeats only the existing owned cleanup operation, and does not retry provider
+work or create another runtime.
 
 Ordinary drive-absolute paths accept backslashes, forward slashes, or mixed
 separators. File identity retains the original requested spelling. Separator