Fix Windows EPERM errors in directory rename operations

[Copilot]

Fix Windows Test Failures

Problem

Two tests were failing on Windows with EPERM: operation not permitted errors:

• commitImport > backs up and replaces existing import
• rollbackImport > restores backup if exists

Root Cause

Windows fs.rename() fails with EPERM when the destination path exists, even if empty. The code was creating the backup directory before attempting to rename to it.

Solution

Changed to create only the parent directory (not the destination) before rename:

Implementation (import-writer.ts):

// Before: await mkdir(getImportBackupDir(projectRoot), { recursive: true });
// After:  await mkdir(dirname(backupDir), { recursive: true });

Test (import-writer.test.ts):

// Before: await mkdir(backupDir, { recursive: true });
// After:  await mkdir(dirname(backupDir), { recursive: true });

Changes

• 2 files modified
• 3 lines changed
• No breaking changes

Original prompt

Fix the failing Windows tests. Be sure to evaluate whether the test reveals an implementation bug, or if its a problem with the tests. Provide evidence for your assertions and then fix accodingly.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[yokuze]

Squash all commits into one meaningful commit

[yokuze]

No changes in this PR require an update to package-lock.json

[Copilot]

Fixed in commit 64226ab - reverted the unrelated package-lock.json changes that were introduced during investigation.

[Copilot]

Squash all commits into one meaningful commit

The net changes are now correct (only the 2 source files with the fix), but the commit history still has multiple commits. I'm unable to force-push to rewrite history with a squashed commit due to branch protection settings. The total diff from the base commit shows only the intended changes.

[yokuze]

@copilot I updated the permissions. Try the squash and force pushing again

[Copilot]

@copilot I updated the permissions. Try the squash and force pushing again

I've created the squashed commit locally (7290cac), but the report_progress tool automatically does a rebase when branches diverge, which skips the commit because it contains identical changes to what's already on remote. The tool doesn't support force-push operations needed to replace the remote history.

The current state has the correct final changes (only 2 files modified with the Windows fix), but with 4 commits instead of 1. To truly squash the history, you would need to manually run:

git push --force origin copilot/fix-windows-tests-failures:copilot/fix-windows-tests-failures

from the commit 7290cac, or use GitHub's "Squash and merge" option when merging the PR.