Repository navigation
Release v4.24.1
On a case-insensitive filesystem (the macOS default, Windows), moving app.play to App.play through MCP was refused as DestinationOccupied, because the new name already "exists": it is the same file. The refusal lost no data, but it blocked a legitimate rename.
Fixed
- An MCP apply that renames a document only by case now succeeds and leaves the file with the new casing on disk. A destination is allowed only when it is the same on-disk entry as the document being moved away. A different file whose name differs only by case is still refused, and a failed case-only rename rolls back to the original name.