Description

### [Critical Bug] Revert Fails to Restore Files After AI Moves Them Between Folders — Files Deleted Not Restored

• Revert causes irreversible data/file loss, which is the opposite of what a revert operation should guarantee

When the AI moves files from an existing folder (e.g. Folder A) to a newly created folder (e.g. Folder B), triggering Revert does not restore the original state correctly.
Instead of moving the files back to Folder A, the revert operation only deletes them from Folder B — resulting in permanent file loss with no recovery.

Expected Behavior

• Revert should fully restore the initial state
• Files that were moved from Folder A → Folder B should be moved back to Folder A
• Folder B (if it didn't exist before) should be removed
• No files should be lost or deleted during the revert process

Actual Behavior

• Files are deleted from Folder B ✅
• Files are NOT restored to Folder A ❌
• Files are permanently lost with no recovery path ❌
• The workspace is left in a broken intermediate state ❌

Plugins

No response

Kilo version

7.2.xx

Steps to reproduce

1. Open Kilo Code with a project containing files in Folder A
2. Send a prompt that causes the AI to:

• Move files out of Folder A
• Create a new Folder B
• Place the moved files into Folder B

3. Trigger the Revert function to restore the initial state
   4.Observe that files are deleted from Folder B but never copied back to Folder A

Screenshot and/or share link

AI Action:
Folder A [file1, file2] → Folder B [file1, file2] (newly created)

Expected Revert:
Folder B [deleted] → Folder A [file1, file2] ✅

Actual Revert:
Folder B [deleted] → Folder A [empty] ❌ (files permanently lost)

Operating System

Windows 25h2

Terminal

No response