openclaw - 💡(How to fix) Fix EPERM on Windows during skills update - movePathWithCopyFallback only catches EXDEV

EPERM on Windows during openclaw skills update --all

Environment

• OS: Windows 11 (10.0.26200)
• OpenClaw: 2026.5.27
• Node: v24.15.0

Problem

Running openclaw skills update --all fails with EPERM on every skill:

Error: EPERM: operation not permitted, rename '...\skills\skill-name' -> '...\skills\.openclaw-install-backups\skill-name-...'

Root Cause

In dist/replace-file-C7_Inj8B.js, the movePathWithCopyFallback$1 function catches only EXDEV to trigger the copy fallback, but on Windows when the Gateway process is watching the skills directory (for hot-reload), rename returns EPERM instead:

// Current code (line ~445)
} catch (error) {
    if (error?.code !== "EXDEV") throw error;
    // EPERM is NOT caught → throws instead of falling back to copy
}

Fix

Add EPERM to the catch condition so it also falls back to copy+rename:

} catch (error) {
    if (error?.code !== "EXDEV" && error?.code !== "EPERM") throw error;
}

Why this is safe

The copy fallback (copyEntryWithManifest + guardedRename) is already implemented and handles directories correctly. It just wasn't being triggered for EPERM errors. On Windows, EPERM during rename is a common scenario (file locking by other processes) and should use the same fallback as EXDEV.

Suggested fix location

File: src/infra/replace-file.ts (or the compiled dist/replace-file-C7_Inj8B.js) Function: movePathWithCopyFallback$1