Fix createTerminal command to prompt for project selection in multiroot workspaces

[Copilot]

Implementation Plan for Multiroot Create Terminal Support

• Explore repository structure and understand the issue
• Identify the actual problem in the current implementation
• Implement solution to prompt for project selection in multiroot workspaces
• Add tests for the new behavior
• Build and verify the extension compiles successfully
• Run code review
• Run security checks
• Fix ESC cancellation bug
• Resolve merge conflicts with main branch

Summary

Successfully implemented multiroot workspace support for the "Python: Create Terminal" command and addressed feedback.

Changes in This Update:

Bug Fix: ESC Cancellation

• Changed if (pw) to if (!pw) return undefined; to make early return explicit when user cancels
• This ensures no terminal is created when the user presses ESC to cancel project selection

Merge Conflict Resolution

• Reorganized imports alphabetically to match main branch
• Updated helper.ts from main branch to include setupNonThenable function
• Replaced manual thenable setup (env.setup((e: any) => e.then)...) with setupNonThenable(env) helper
• Used existing directories (/tmp, /home) in tests instead of stubbing fs.stat

All Tests Passing

✅ 250 tests passing
✅ All Create Terminal Command tests passing (5/5)

Behavior:

Before: When Python extension called python-envs.createTerminal, it would directly create a terminal without checking for multiple projects. ESC handling was implicit.

After:

1. Checks all Python projects
2. If 1 project: creates terminal (no prompt)
3. If > 1 project: prompts user to select
4. If user cancels (ESC): returns undefined explicitly - no terminal created

Original prompt

---

This section details on the original issue you should resolve

<issue_title>'Python: Create Terminal' doesn't consider multiroot option</issue_title>
<issue_description>I have a workspace with two folders each with their own Python virtual environment.

Invoking the Python: Create Terminal command automatically creates a terminal for the first project in the workspace. We should unify this with the Python environments extension. If there is more than one Python project in the workspace ask which project to create a terminal for.</issue_description>

Comments on the Issue (you are @copilot in this section)

@eleanorjboyd the desired behavior is as such: 1. user selects `Python: Create Terminal` 2. check number of python projects 3. if project count = 1 just open this environment 4. if project count > 1, show a quick pick for the user to select which project (and listing that environment) they want to open the terminal for.

• Fixes 'Python: Create Terminal' doesn't consider multiroot option #291

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[eleanorjboyd]

@copilot
found a bug. When presented with the menu to select between workspaces, clicking "esc" will create a terminal when it should instead do nothing as user didn't select anything

secondly fix merge conflicts for the unit test file

[Copilot]

@copilot
found a bug. When presented with the menu to select between workspaces, clicking "esc" will create a terminal when it should instead do nothing as user didn't select anything

...

Fixed both issues in commit 122bb6f:

ESC Bug: Made the early return explicit when user cancels - changed from if (pw) { ... } to if (!pw) return undefined; to clearly show no terminal is created when ESC is pressed.

Merge Conflicts: Resolved by:

• Reorganizing imports alphabetically to match main
• Replacing manual thenable setup with setupNonThenable() helper
• Updating helper.ts from main to include the new function
• Using real directories (/tmp, /home) in tests instead of stubbing fs

All 250 unit tests passing, including the 5 new Create Terminal tests.