`Python: Create Environment` command fails to start console

System details:

Positron and OS details:

Positron Dev Version: 2025.08.0 build 0
Code - OSS Version: 1.100.0
Commit: c08ec0bf (main)
Date: Unknown
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Interpreter details:

Python

Describe the issue:

The Python: Create Environment command sometimes fails to start up the Console.

Steps to reproduce the issue:

1. Create a new workspace with a new venv (I used the New Folder Flow)
   • I tried the venv option and uv option here
2. Run Python: Create Environment and choose an option
   • I tried the venv option and uv option here too
3. If you choose "Use Existing", the console shuts down and doesn't start a new console

The "Delete and Recreate" option seems to work fine.

Expected or desired behavior:

New environment should always start

Were there any error messages in the UI, Output panel, or Developer Tools console?

Sometimes in the Python Language Pack logs I see
New environment has already been selected
Sometimes it's just
createPythonRuntime: startup behavior: implicit

Start by reproducing the Python: Create Environment flow with a new workspace, trying both venv and uv and then the Use Existing option. Read the Python Language Pack logs and Developer Tools console around the shutdown; done means selecting an existing environment reliably starts a new console without the reported startup messages.