`.vscode/tasks.json` is used when `.zed/tasks.json` presents

[54wedge]

Reproduction steps

1. Create these json file in an empty project folder

.vscode/tasks.json

{
    "tasks": [
        {
            "type": "shell",
            "label": "test",
            "command": "echo",
            "args": [
                "vscode"
            ],
            "options": {
                "cwd": "${workspaceFolder}"
            },
        }
    ]
}

.zed/tasks.json

[
  {
    "label": "test",
    "command": "echo",
    "args": [
        "zed",
    ],
    "cwd": "$ZED_WORKTREE_ROOT",
    "use_new_terminal": false,
    "allow_concurrent_runs": false,
    "reveal": "no_focus",
    "hide": "never",
    "shell": "system",
    "show_summary": true,
    "show_command": false
  }
]

.zed/debug.json

[
  {
    "label": "Debug test",
    "build": "test",
    "adapter": "CodeLLDB"
  }
]

2. Use tasks:spawn and there are two tasks available. Sometimes, there is only the vscode one depending on what was the last used task.
3. In debug panel, start debug session. The vscode build task is used every time.

Current vs. Expected behavior

In #32590, this issue is claimed to be fixed. I expect to see only tasks from .zed/tasks.json in tasks spawn menu and a debug session should only spawn build task from .zed/tasks.json as well.

Zed version and system specs

Zed: v0.227.1+stable.199.9f9b707d39d62468d4cdaed2d8eb95a847da4cf9 (Zed)
OS: macOS 15.0
Memory: 16 GiB
Architecture: x86_64

Attach Zed log file

Relevant Zed settings

No response

Relevant Keymap

No response

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

None

[yeskunall]

It sounds like #32590 didn’t handle all cases -- thanks for the report @54wedge.