Automated terminal activation kills all running tasks in terminals

@anthonykim1 đang làm issue này rồi.

Từ ngày 23/3/2026.

When I run `uv sync` on a freshly-cloned project, VS Code detects the new virtual environment, and activates it in all terminals.

However, in order to do this, it sends an interrupt signal in all terminals, causing most running tasks to exit. This is incredibly annoying in some projects, especially as the action can sometimes occur randomly up to 2 minutes after the virtual environment is created.

## To reproduce

1. `git clone` a Python project
2. Start up the project, eg by running `uv run [program]`
3. UV creates the virtual environment and starts the program
4. VS Code then immediately kills the freshly-started program

## Why this is incredibly disruptive to my workflow

I work as a university tutor. I am currently assignment marking, and to do so I must `uv run` large numbers of student projects. Every time I do this, VS Code kills their project part-way through testing.