How to reproduce:
1. Create and open a new project
2. Create a new Script file in the Project tab
3. Right after creating, create any other script-based file in the Project tab (but do not validate the name, leave it in the renaming state)
4. Observe the Project tab

Expected result: The new file stays in the naming state (which then allows finishing creating the file)
Actual result: The new file leaves the naming state (which finishes creation of the file, leaving it as a ghost file)

Reproducible in: 6000.2.0b2, 6000.2.0f1, 6000.3.0a1
Not reproducible in: 6000.0.55f1, 6000.2.0b1, 6000.3.0a4
Fixed in: 6000.3.0a2

Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested

Notes:
- The “script-based“ files would be (MonoBehavior scripts, Assembly Definition files, Shaders, etc.) - anything that contains scripts/is text-based, that is compiled after the naming state
- Invoking script recompilation in any other way also can reproduce the bug (e.g. moving scripts/asmdef files)
- Trying to delete the ghost file will attempt to delete the root folder
- Creating a new file will delete the ghost file