Prevent enable si showing up when using pwsh from chat with accessibility mode

[anthonykim1]

Resolves: #307698

Before:

After:

afterEnableFix.mp4

Two parts to this:

• timeout bump for A11y: We add extra 3 second when waiting for shell integration with accessible mode toggled, since we remove and load our bundled PSReadLine in our shell integration script. This would allow us for the first command to chat gets proper command detection.
  • Without the timeout bump we get

• Deferred banner: Instead of deciding whether to show "enable shell integration banner" right before running command, we should wait until command finishes,
  • Without the deferred banner we get the enable shell integration message again

[Copilot]

Pull request overview

Adjusts RunInTerminalTool’s “Enable shell integration” guidance so it doesn’t appear when shell integration is already enabled via settings, addressing the misleading warning seen in accessibility/screen reader scenarios.

Changes:

• Import TerminalSettingId to read the shell integration enablement setting.
• Gate the “Enable shell integration…” info message on both shellIntegrationQuality === None and terminal.integrated.shellIntegration.enabled !== true.

Show a summary per file

File	Description
src/vs/workbench/contrib/terminalContrib/chatAgentTools/browser/tools/runInTerminalTool.ts	Suppresses the “Enable shell integration…” prompt when shell integration is already enabled in configuration.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[github-actions]

Screenshot Changes

Base: 7f3ec374 Current: 8384ad7f

Changed (1)

editor/inlineCompletions/other/JumpToHint/Dark

Before	After

---

blocks-ci screenshots changed

Replace the contents of test/componentFixtures/blocks-ci-screenshots.md with:

Updated blocks-ci-screenshots.md

<!-- auto-generated by CI — do not edit manually -->

#### editor/codeEditor/CodeEditor/Dark
![screenshot](https://hediet-screenshots.azurewebsites.net/images/cb32a3e854b5734fe5aaca2318f2e0a42ee821b05ea97883ea42c5ba95edb3c3)

#### editor/codeEditor/CodeEditor/Light
![screenshot](https://hediet-screenshots.azurewebsites.net/images/42624fbba5e0db7f32c224b5eb9c5dd3b08245697ae2e7d2a88be0d7c287129b)

[anthonykim1]

@meganrogge was right, powershell 7 did not show the `enable shell integration warning` whereas windows powershell did.

[anthonykim1]

The shell integration banner decision is deferred to after command execution completes (see below). This gives SI time to arrive — on Windows PowerShell 5.1, cold-loading PSReadLine can push HasRichCommandDetection past the initial wait timeout, and checking here would incorrectly show the banner.