Revert "chore: terminate all tasks after debug"

[Patrick-Erichsen]

Reverts #6405

This is causing an issue where every time you reload the debug window, all the processes are terminated.

---

Summary by cubic

Removed automatic termination of all tasks after debugging to prevent processes from being killed when reloading the debug window.

[netlify]

✅ Deploy Preview for continuedev canceled.

Name	Link
🔨 Latest commit	92d1df2
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/686ee612061f2b0008d56389

[cubic-dev-ai]

cubic reviewed this PR and found no issues. Review PR in cubic.dev.

[Patrick-Erichsen]

@uinstinct reverting the commit for now, but it would still be nice to have the original feature that you were trying to do here, so might be worth a second shot!

FWIW, here's what Claude 4 had to say about the issue, seems like it might not be possible if this is true:

The problem is that the postDebugTask is set to "Terminate All Tasks" which terminates all tasks when the debug session ends. However, when you reload the debug window (as opposed to fully stopping it), VS Code is treating this as the debug session ending and triggering the postDebugTask.

Let me check if there's a way to distinguish between a reload and a full stop in VS Code's debug configuration, or if we need to modify the approach.

Looking at the current configuration:

The postDebugTask is set to "Terminate All Tasks"
The "Terminate All Tasks" task uses workbench.action.tasks.terminate with terminateAll argument
This terminates ALL tasks, but apparently one task (npm run esbuild-notify) survives
The issue is that VS Code doesn't distinguish between a reload and a stop when it comes to postDebugTask. Both actions trigger the post-debug task.