manage_scene.create creates nested .unity path when name and full path are both provided

[reefbarman]

Summary

manage_scene with action: "create" creates an unexpected nested path when both name and a .unity path are provided.

Environment

• Unity: 6000.3.7f1
• Package: com.coplaydev.unity-mcp (@0bad2d0f59a0, from stack path)
• OS: Windows 11 x64

Repro

Call:

{
  "action": "create",
  "name": "MainScene",
  "path": "Assets/Scenes/MainScene.unity"
}

Actual result

Response:

{
  "success": true,
  "message": "Scene 'MainScene.unity' created successfully at 'Assets/Scenes/MainScene.unity/MainScene.unity'.",
  "data": {
    "path": "Assets/Scenes/MainScene.unity/MainScene.unity"
  }
}

So it creates:

• Assets/Scenes/MainScene.unity/MainScene.unity

Expected result

Create exactly:

• Assets/Scenes/MainScene.unity

If both name and path are supplied, either:

1. path should be treated as the full destination file path, or
2. name should be ignored/validated when path already includes a filename.

Notes

This behavior cascades into follow-up calls (load, build scenes) because consumers expect the provided path to be the created scene path.