Windows: PowerShell aliases are unavailable in the integrated terminal

[larock22]

Summary

On Windows 11, aliases/functions from the user's PowerShell setup are not available inside Athas' integrated terminal when using Windows PowerShell or PowerShell Core.

Steps to Reproduce

1. On Windows 11, define a PowerShell alias or function in the normal PowerShell profile.
2. Confirm the alias works in an external Windows PowerShell or PowerShell Core session.
3. In Athas, choose Windows PowerShell or PowerShell Core as the integrated terminal shell.
4. Open a new integrated terminal.
5. Run the alias/function from that terminal.

Expected Behavior

The integrated terminal should behave like a normal interactive PowerShell session and make the user's PowerShell aliases/functions available.

Actual Behavior

The alias/function is not available in the Athas integrated terminal.

Operating System

Windows 11

Version

0.7.0-preview.1

Logs or Screenshots

Code-path notes from local research:

• Windows shell discovery registers powershell.exe and pwsh.exe in crates/terminal/src/shell.rs.
• Terminal launch constructs CommandBuilder::new(&shell_path) for the selected shell in crates/terminal/src/connection.rs.
• On Windows, terminal environment handling currently inherits std::env::vars() from the Athas process in crates/terminal/src/connection.rs.
• The selected shell and working directory are sent from src/features/terminal/components/terminal.tsx into the Tauri create_terminal command.

Checklist

• I searched existing issues first.
• I reproduced this on the latest available version.