jif 80b88a700e Avoid false URL-launch detections in literal PowerShell commands (#54076) ...

## Why

PowerShell safety checks can mistake a literal `start` argument for a URL-launch command, or combine a process launch with a URL from a separate command.

## What changed

Classify independently parsed literal PowerShell commands separately so commands such as `Write-Output start 'https://example.com'` do not trigger URL-launch checks. Retain conservative checks for pipelines, script state, executable strings, and shell or terminal wrappers, while continuing to detect actual URL launches and destructive commands.

## Testing

Add policy regression coverage for literal arguments, separate commands, URL launches, wrappers, and destructive commands, plus a Windows integration test covering execution and policy rejection.

GitOrigin-RevId: 2878aa86bc36b44c60230cc1de3430922b28b81a

2026-10-14 19:47:50 +00:00

..

src

Avoid false URL-launch detections in literal PowerShell commands (#54076)

2026-10-14 19:47:50 +00:00

BUILD.bazel

Add a fail-closed Tree-sitter PowerShell lowerer (#39213)

2026-08-18 14:59:43 +00:00

Cargo.toml

Move shell snapshot tests into shell-command (#39480)

2026-08-19 12:56:08 +00:00