feat: log effective Windows local runtime shell

[C10H14N2O5]

TL;DR

• Log effective Windows shell once when LocalBooter is created
• No behavior change to pwsh/powershell selection
• Tests + Win E2E for both branches

Background

Fixes #9642

PR #9622 introduced automatic Windows shell selection for the Local Runtime, preferring PowerShell 7 (pwsh.exe) when available and falling back to Windows PowerShell 5.1 (powershell.exe) otherwise.

While this removes the need for an additional configuration option, the selected shell is not directly visible to users. In environments where PATH differs between the process launching AstrBot and an interactive terminal—for example, when AstrBot is started by a launcher—the runtime may unexpectedly fall back to Windows PowerShell 5.1 even though pwsh.exe is installed and available elsewhere.

Without any indication of the effective shell, this is typically only discovered later when a PowerShell 7-specific command or syntax fails.

This PR addresses that observability gap by logging the shell selected by the Windows Local Runtime.

---

Modifications / 改动点

This PR adds observability for the effective shell selected by the automatic shell detection introduced for the Windows Local Runtime in PR #9622.

When the Local Runtime singleton is first created, it logs the selected PowerShell executable using the existing Windows shell resolution logic:

• When PowerShell 7 is available, pwsh.exe is logged;
• When PowerShell 7 is unavailable and the runtime falls back to Windows PowerShell 5.1, powershell.exe is logged;
• The log is emitted only once when the Local Runtime singleton is first created and is not repeated on subsequent Shell Tool calls;
• The existing shell resolution logic from feat: support PowerShell 7 for Windows local shell #9622 is reused without changing the current PowerShell 7 preference or Windows PowerShell 5.1 fallback behavior.

Example:

[Computer] Windows local runtime shell: pwsh.exe

Or:

[Computer] Windows local runtime shell: powershell.exe

Unit tests are also added to cover:

• Logging pwsh.exe when the Windows shell resolver returns it;

• Logging powershell.exe when the Windows shell resolver returns the fallback;

• Avoiding Windows shell resolution and the corresponding log on non-Windows platforms;

• Ensuring repeated retrieval of the same Local Runtime singleton does not resolve or log the shell again.

• This is NOT a breaking change. / 这不是一个破坏性变更。

---

Screenshots or Test Results / 运行截图或测试结果

This PR does not include any UI changes, so no screenshots are provided. The following sections show the actual runtime logs and automated test results.

Test Environment

• Windows 11 Home 64-bit
• DisplayVersion: 25H2
• Build: 26200.9168
• Python: 3.14.0
• PowerShell 7: 7.6.4

---

Windows End-to-End Verification: PowerShell 7 Available

When pwsh.exe can be resolved from PATH, the Local Runtime correctly logs:

[Computer] Windows local runtime shell: pwsh.exe

The Agent was then asked in the conversation to execute:

$PSVersionTable.PSVersion.ToString()

Output:

7.6.4

The Agent was subsequently asked to verify PowerShell 7-specific features such as the ternary operator, ??, and $IsWindows, all of which executed successfully.

It was also verified that repeated Shell Tool calls do not emit the effective shell log again, as expected since it is logged only once per singleton lifecycle.

---

Windows End-to-End Verification: Fallback When PowerShell 7 Is Unavailable

After temporarily removing PowerShell 7 from the current process's PATH and restarting AstrBot, the Local Runtime correctly falls back and logs:

[Computer] Windows local runtime shell: powershell.exe

The Agent was then asked in the conversation to execute:

$PSVersionTable.PSVersion.ToString()

Output:

5.1.26100.8972

PowerShell 7-specific syntax was also verified to be unavailable in this environment, confirming that the actual shell being executed was Windows PowerShell 5.1.

A subsequent Shell Tool call likewise did not emit the effective shell log again.

---

Automated Tests

New #9642 logging tests:

3 passed

Regression tests related to #9642 and #9622:

13 passed

Formatting and static checks:

uv run ruff format --check .
500 files already formatted

uv run ruff check .
All checks passed!

git diff --check
No whitespace errors

Five pre-existing failures were observed when running a broader set of related tests on Windows. The same five failures were reproduced unchanged in an independent detached worktree using the unmodified baseline commit 5e40eb4b522ea8cbe30ddbc2e3bff8ca18c7b166, confirming that they are not regressions introduced by this PR.

---

Checklist / 检查清单

• 👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  / 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。

• 😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  / 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。

• 🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  / 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到 requirements.txt 和 pyproject.toml 文件相应位置。

• 😮 My changes do not introduce malicious code.
  / 我的更改没有引入恶意代码。

Summary by Sourcery

Log the effective Windows shell used by the local runtime when the LocalBooter singleton is first created, and ensure this behavior is covered by unit tests.

New Features:

• Add a one-time informational log indicating the resolved Windows PowerShell executable for the Windows local runtime.

Tests:

• Add unit tests verifying the Windows shell is logged once per LocalBooter singleton on Windows and skipped on non-Windows platforms.

Summary by Sourcery

Log the effective Windows shell used by the local runtime when the LocalBooter singleton is first created.

New Features:

• Emit a one-time informational log indicating the resolved Windows PowerShell executable for the Windows local runtime on Windows platforms.

Tests:

• Add unit tests ensuring the Windows shell is logged once per LocalBooter singleton on Windows and that shell resolution/logging is skipped on non-Windows platforms.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}